BEWARE! Some of the information presented in er might be confidential! Here comes the first news: 90.09.27 Table of contents: 1. Using an 8MB machine or how is life with only 120Mb disk space. 2. Pre GA Hardware problems and upgrades 3. Questions and answers about NextStep 4. Some statements about X-stations ********************************************************************* 1. Using an 8MB machine or how is life with only 120Mb disk space: For those that try to use 8MB systems or 320 machines with only a 120Mb hardfile, there might be some intersting info in a text one of our colleagues wrote. Get it with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET STORAGE TEXT ********************************************************************* 2. Pre GA Hardware problems and upgrades: The information in this article is to be treated as IBM CONFIDENTIAL! Attention All Marketing Support and Vendor Support Personnel: The purpose of this note to make you aware of the latest entry on the ASAP "Early Warning" forum. It describes some of the situations which have been found to occur on RISC/6000 systems running AIXv3 on pre-GA level hardware. (Serial numbers below 5000). There are different release levels of pre-GA hardware. Some of the situations occur only on certain hardware levels and particular configurations. If vendors / customers experience symptoms described below, there is a high probability that the machine is not at GA level. IBM plans to replace/upgrade all the pre-GA level systems with GA-level hardware. The problems identified below will be fixed when machines are upgraded to GA level. Users should not be directed to replace hardware to resolve the identified problems. If a customer is severely impacted by any of the problems documented below, a process exists to expedite a GA upgrade on their machine and can be arranged through your area marketing coordinator. It is important that this information be disseminated to appropriate RISC/6000 support personnel. The following is a list of hardware components known to have caused problems when used with GA-level software. Display Adapters: SABINE High-Performance 3D Color Graphics Display Adapter- There are three potential problems associated with "SABINE" both the high performance 8 bit and the 24 bit color display assemblies. 1. Dirty Pixels - Pixels that appear on the screen in random and intensifies with time to form horizontal display stripes across the screen. 2. Popping Pixels - Pixel noise that appears and disappears onto the screen in a random pattern, giving a visual appearance of light snow. 3. Water Fall - Horizontal noise displayed onto the screen that gives a visual appearances of water rippling across. This occurs only on Llanos with 225V power supply. SKYWAY Color Graphics Display Adapter- Both the grayscale and color graphic assemblies are experiencing situations similar to the "Water Fall" symptom described for the SABINE Display adapter, in which horizontal noise displayed onto the screen that give a visual appearances of water rippling across. This occurs only on Llanos with 225V power supply. L.A.N. Adapters: ETHERNET High-Performance LAN Adapter- The "ETHERNET" AT Form Factor assembly performs rather poorly under heavy stress. If NFS operations are being done between two machines and NFS is the only application using the network, then performance degrades very quickly. A hardware engineering change to the AT Form Factor is being generated and should alleviate many of problems currently being experienced. With the ship level "ETHERNET" PS/2 Form Factor cards PN 71F1152, 71F1182, AND 71F1183 , NFS and general network performance will be what is expected. HARD DRIVES: 320 MB HARDFILE part # 93X2355 / EC# 843811 does not support system down loadable ucode upgrades. To upgrade the microcode on this drive, the microcode module must be replaced. 120 MB HARDFILE part # 6128261 / EC# A07259 has I/O channel performance problems when two or more devices are added to the bus. The next level of drive PN 6128264 / EC# C13077 is required. COMMO Devices: 8 PORT RS232 card PN 59F3015 / EC# C25944 has a signal noise crosstalk problem and does not work with a 320 DEC terminal. The next level of card PN 59F3796 / EC# C25985 is required. 8 PORT MIL188 card PN 59F4037 / EC# C26213 does not recognize that the printer is disconnected or powered down, therefore it sends data to the bit bucket. The next level of card PN 81F8105 / EC# C26469 is required. TAPE DRIVES: The 1/2" TAPE DRIVE (table top), PN 21F7902 / EC# 840180 hangs after IPL. The next level of tape drive PN 21F7902 / EC# 894182 is required. The 1/2" TAPE DRIVE (rackmount), PN 21F7901 / EC# 840180 hangs after IPL. The next level of tape drive PN 21F7901 / EC# 894182 is required. The Model 7207 (LUGE) 1/4" Tape Drive- There are three known problems affecting the 7207-001 tape drive: 1) Unable to read files written with optional ECC mode "ON", especially by non-7207 1/4-inch tape drives. 2) The 7207-001 tape drive is NOT in full compliance with the tape interchangeability QIC 120/150 standard. This means that there is a possibility that the data cannot be read on some non-IBM tape drives. 3) There are a select number of early level tape drives that may experience difficulty in installing General Availability(GA) level LPPs using the 'ALL' option in the System Management Omterface Tool (SMIT). IBM will repair/replace the tape drive(s), but in the meantime, as a way to avoid these problems, we strongly recommend that you implement the following three procedures: 1) For the ECC problem, disable (turn off) the ECC feature. This is accomplished through SMIT. The default condition for ECC is enabled (on). Disabling ECC provides save/ restore capabilities with the equivalent error detection typically found in the industry today. ECC should remain disabled (off) until the tape drive is repaired/replaced. 2) For the QIC 120/150 problem, before attempting data interchange with non-IBM tape drives, conduct tests for interchangeability. 3) For the early level tape drives, install your LPPs individually instead of using the 'ALL' option in SMIT. CPU PLANAR: The chart below shows what fixes have been implemented with each level of planar. (X= implemented) Time Of Day - Supports TOD clock fix on the I/O planar. IPL evoke from tape - Supports IPL from tape. COMBO chip fix - Micro channel refresh, enhances parity checking capability. FPU 2.3 - Store executes out of order with precision arithmetic op. FPU 2.4 - Round to single precision may get incorrect results. FPU 2.5 - No known problems. FPU 3.1 - No known problems. ROS level - Different level of IPL ROS code. Model 530- WICHITA TOD IPL COMBO 2.3 2.4 2.5 3.1 ROS ------- --- --- ----- --- --- --- --- ---- 59F3583 - - - X - - - 7/28 59F4403 - - - X - - - 7/28 71F0240 - - X - X - - 12/22 71F0867 X X X - - X - 2/20 81F7872 X X X - - X - 3/07 81F7784 X X X - - - X 3/07 81F7739 X X X - - - X 3/07 Model 520- ARANSAS TOD IPL COMBO 2.3 2.4 2.5 3.1 ROS ------- --- --- ----- --- --- --- --- ---- 59F3591 - - X X - - - 7/28 71F0877 X X X - - X - 2/20 71F1140 X X X - - X - 3/07 81F7779 X X X - - - X 3/07 71F0030 X X X - - - X 3/07 Model 320- LLANO TOD IPL COMBO 2.3 2.4 2.5 3.1 ROS ------- --- --- ----- --- --- --- --- ---- 59F3597 - - - X - - - 7/28 70F9650 - - - X - - - 7/28 70F9928 - - X - X - - 12/22 71F0862 X X X - X - - 2/20 81F7877 X X X - - X - 3/07 81F7774 X X X - - - X 3/07 71F0044 X X X - - - X 3/07 --------------------------------------------------------------- *********************************************************************** 3. Questions and answers about NextStep IBM Press Statement IBM TO SUPPORT LATEST RELEASE OF NEXTSTEP SOFTWARE ENVIRONMENT WHITE PLAINS, N. Y., Sept. 18. . . IBM announces that it plans to adopt the new release of NeXT* Computer, Inc.'s NeXTstep* application software development and user interface environment. "NeXTstep Release 2.0 provides the power of color and the improved function that will appeal to many of our customers and software developers," said Bill Filip, assistant general manager, Marketing, for IBM's Personal Systems organization. "This offering will enhance IBM AIX** operating system platforms such as the RISC System/6000**, increasing ease-of-use and productivity. IBM intends to support NeXTstep Release 2.0 in a future release of our AIX NeXTstep products." In addition to the support for color, customers and software developers will benefit from other NeXTstep Release 2.0 enhancements such as the more powerful Workspace Manager, expanded European language support, and an improved Interface Builder that will make it even easier to customize an application interface. As a development environment, it has broad appeal for users in fields such such as higher education, banking, communications, medical applications and research. IBM and NeXT have worked together since 1988. The relationship has included software licensing and patent licensing agreements. # # # * Indicates trademark or registered trademark of NeXT Computer, Inc. ** Indicates trademark or registered trademark of International Business Machines Corporation # Indicates registered trademark of American Telephone & Telegraph (For more information, contact IBM Media Relations, (914) 642-4634.) QUESTIONS AND ANSWERS RELEASE 2 Q) What customer benefits do you see in Release 2.0? A) In addition to the support for color, customers and software developers will benefit from other NeXTstep Release 2.0 enhancements such as the more powerful Workspace Manager, expanded European language support, and an improved Interface Builder that will make it even easier to customize an application interface. As a development environment, we see broad appeal for users in fields such such as higher education, banking, communications, medical applications and research. You should speak to NeXT for more details on the new product. Q) When will IBM incorporate NeXTstep Release 2.0 into its AIX products? A) We will announce our plans at a later date with regard to Release 2.0. We believe that customers will find that color and other functional enhancements will make Release 2 a robust graphical user interface and development environment. Our customers will want to take advantage of these features, and it is our intent to deliver this capability. Q) Why didn't IBM participate in NeXT's announcement event? A) NeXT's announcement involved new products announced by NeXT, not by IBM. Since IBM was not announcing any new products, there was nothing out of the ordinary in our not participating. RELEASE 1 Q) IBM is supposed to be making available its PS/2 and RISC System/6000 AIX NeXTstep Release 1-based products in the third quarter. What is the status of this? A) In light of the new NeXTstep release announced today, IBM is reviewing our activities with respect to Release 1 on the PS/2 and RISC System/6000. We will announce our plans relative to Release 1 later this month. Q) Are you halting delivery? What about those customers who have ordered Release 1-based products? A) We will be confirming our plans to our customers later this month. It is our intent to offer AIX products that take advantage of the latest NeXT technology, which provides an easy-to-use interface as well as an enhanced development environment for software application developers. Q) It looks like you will be delaying introduction of Release 1 on the RISC System/6000. Is that because customer response has been poor? A) With the announcement of Release 2.0, IBM is now reviewing our plans with respect to NeXTstep implementation on our AIX platforms. The additional capabilities, including color, make Release 2.0 an attractive offering that would complement our AIX platforms. We want to make it available as soon as our development schedule permits. Q) Have any vendors expressed interest in porting to AIX NeXTstep? A) Yes, a number of key vendors have expressed an interest in porting to AIX NeXTstep. Companies who have done so include Wolfram, Frame, Ashton Tate, WordPerfect, Media Logic, Adobe, Lotus and StepStone. IBM intends to increase its software vendor support activities for the AIX NeXTstep environment in preparation for Release 2.0 availability. Q) Have any customers indicated an interest in porting their applications on to AIX NeXTstep? A) Yes. We have seen significant customer interest, for example, in working with the early code in the AIX NeXTstep offering on the RISC System/6000. These customers represent such market segments as higher education, health care, communications, banking/finance and research laboratories. MOTIF, NEXTSTEP Q) IBM offers a Motif-based graphical user interface for the RISC System/6000 that is already available as well as the NeXTstep offering planned for introduction this month. How have your orders been for both environments? A) IBM does not break out specific orders by GUI. We will continue to offer both environments to our customers as part of IBM's commitment to respond to our customers' requirements for enhanced ease-of-use and productivity. Q) How does NeXTstep Release 2.0 compare to OSF/Motif? A) It is IBM's intent to provide our customers with the best products to meet their needs. Both Motif and NeXTstep contain graphical user interface environments that provide ease of use and productivity enhancements. As customers have differing requirements, they will choose the product that best meets their own needs. Motif has wide acceptance in the UNIX marketplace as an industry leader. IBM NEXT/RELATIONSHIP Q) What is your current relationship with NeXT? A) IBM has been working with NeXT for more than two years, and we have a software licensing and a patent licensing agreement. While specifics of our agreements are considered confidential, I can tell you that our two companies are committed to continuing to make the NeXTstep technology available to customers on IBM AIX platforms. IBM has licensed the NeXT technology, allowing us to incorporate it into products that would run on IBM AIX platforms such as the RISC System/6000. Q) IBM states that they have had a relationship with NeXT for the past two years...there is no evidence that the two companies are committed to working together. Did IBM just licence NeXTstep to cover all bets? A) IBM is very committed in its support of the NeXTstep product and the benefits it offers to our customers and to software developers who provide applications for IBM AIX platforms. We intend to provide AIX NeXTstep Release 2.0 products, and will announce our plans at a later date. AIX DIRECTIONS Q) Will you be announcing any NeXTstep activity with respect to AIX/370? A) NeXTstep is a desktop graphical user interface and development environment. We have no plans for an AIX/370 NeXTstep offering at this time. Q) IBM has indicated that it will be adopting the OSF/1 technology on the PS/2 as its UNIX offering on the low-end. How will that affect your directions with respect to NeXTstep on the PS/2? A) IBM has not yet announced detailed plans for our OSF/1 product on the PS/2. When we do, specifics on the NeXTstep offering will be included. Q) Any more information on your plans to adopt OSF/1 on your other AIX platforms besides the PS/2? A) IBM has stated its intent to include the OSF/1 base technology into our AIX offering for the PS/2. At this time, we have not announced it for any of our other platforms. IBM supports OSF in its mission to provide the best open industry standards technologies that can be shared throughout the industry. GENERAL ISSUES Q) How have sales been on AIX PS/2? A) The latest release of AIX PS/2 became available in March of this year, and demand has been strong. IBM is committed to providing AIX capability across the range of our product line, and as such, our AIX PS/2 offering on the low-end will remain a strategic product. We have announced our intent to move to the OSF/1 base technology on the next release of AIX for the PS/2, so customers will benefit from the OSF "best of breed" base technology complemented by IBM's value add. We will be announcing more details on our low-end AIX offering later this year. (Note: There have been some supply constraints to the dealers for this product which IBM is working to address.) Q) How have sales been for AIX/370? Will AIX/370 run with the new System/390? A) AIX/370, which became available at the end of March, will run with selected models of the new System/390 family. While demand for a high-end AIX solution is not as great as that for the RISC System/6000 or PS/2, the product is meeting our expectations and we see a fair demand for UNIX capability on the high end. We continue to work with customers in tailoring the product to their needs, and we're in the process of conducting a survey of our installed base right now. (IF NEEDED: We did temporarily halt shipment of the product after it became available for systems assurance reasons. We resumed shipment in July.) Q) How have sales of the RISC System/6000 been? A) IBM is very pleased with customer reactions, and orders are at the high end of our range of expectations. We now have thousands of systems purchased and in place at customer locations. Industry analysts have predicted that we would ship 15,000 units this year, and we expect to exceed that figure. Q) I've heard that there have been RISC System/6000 delays in shipping to certain customers. What can you tell me about that? A) Heavy order demands did cause us to experience delays during our initial volume ramp up, but we are now in a position to deliver a system in 30 - 60 days. IF SPECIFICALLY TOLD THAT A CUSTOMER REPORTED TAPE DRIVE DELAY: We did have a recent situation with a certain type of advanced tape drive, our 150-megabyte external 1/4-inch cartridge tape drive -- where we discovered two problems and temporarily delayed shipments until the fix was implemented. The tape, a new product for us, is provided by a vendor, and the problem has been resolved. (We do not disclose information on the number of customers affected, but it did not present any major delays for customers.) SCSI ISSUE: We have identified a design error in a chip that is located on the SCSI I/O controller and are taking appropriate action to notify our customers so that they are not impacted by this problem. When the Micro Channel is extremely busy the SCSI adapter may not be able to access the bus to transfer data for a significant amount of time. The lack of access to the Micro Channel may permit the SCSI I/O controller to write and erroneous byte of data onto the device or it may write multiple bytes of data into system memory. The problem has the potential of affecting several models. Customers will be able to obtain a fix to circumvent the problem for the model 320; for other models, we have notified customers to limit the machine to two SCSI I/O controllers for now until a replacement is provided in the very near future that will allow more than two to be used. Q) When will IBM deliver a true under $10,000 RISC solution? A) IBM has stated that we intend to provide a low-end, diskless workstation as part of our plans to extend the RISC System/6000 family. Our current product line is very competitive on price, giving us price-performance leadership that we would intend to continue with future offerings. *********************************************************************** 4. Some statements about X-stations PROBLEM SOLVING FOR AN XSTATION 120 How to Read the LAN Statistics Screen The LAN statistics screen is the screen that appears on the Xstation 120 terminal as it is trying to "boot up". Copyright and version information appear at the top of the screen, while relevant LAN features are displayed below. The hardware address of the Ethernet adapter is shown, along with THICK or THIN for the 15-pin or co-axial cable connections. If a Token-Ring adapter is installed, its hardware address is shown, along with the 4Mbps or 16Mbps data rate. In addition, two lines are displayed for each LAN adapter installed. The line(s) labeled "BOOTP" provide information on the transmission/reception of bootp packets, while the line(s) labeled "TFTP" provide information on the transmission/reception of TFTP packets. Reading from left to right, the first group of numbers for the "BOOTP" line of the LAN statistics screen indicates the number of bootp packets sent out by the Xstation 120, the second group of numbers indicates the number of UDP packets received, the third group indicates the number of incorrect packets received, and the fourth group indicates packets that have been sent but have no corresponding response (i.e., time-outs). The "TFTP" line can be interpreted the same way, with the numbers representing TFTP packets sent,received, received in error, timed-out. Sometimes, the fifth set of zeros following the TFTP line contains a number. This is an error code. Token-Ring error codes are 66xx numbers. Ethernet error codes are 88xx numbers. ETHERNET CHECKOUT FIRST things to look for and correct: 1) Check the Xstation 120 jumper block for proper setting: Xstation 120 is shipped with jumpers set to THIN Ethernet connection. If you want to use THICK Ethernet, you must move the jumpers. See your Setup and Operator's Guide for instructions. - (THICK) When using external tranceivers, jumper must be in the FRONT position - (THIN) To use the internal tranceiver, jumper must be in the REAR position 2) Check to see that network & components comply with 802.3. KEY items: - 50-ohm 802.3 cable, connectors and terminations throughout network. One piece of 90-ohm cable can cause dead spots in the network. - solid connections throughout (connectors, cable shields, etc) for proper impedance. 3) For THIN (COAX) Ethernet networks: - no more than 30 stations per segment - no segment over 185 meters in length 4) If (THICK) external tranceiver boxes are used, insure that they are equipped with SQE (heartbeat) and that it is Enabled (ON) in each box. 5) Ethernet Version 1 is NOT SUPPORTED!! Booting Failures The most common booting failure is caused by YP/NIS. If YP/NIS is active, it uses a master services file in place of the /etc/services file. The 3 lines the Xstation Manager adds to the /etc/services file must be copied to the master services file. These 3 lines are: bootps-67/udp bootpc-68/udp x_st_mgrd-7000/tcp Xstation 120 LAN Statistics Screen indicates no bootp packets being sent and an error code of 8803 appears on TFTP line. 6) A THICK Ethernet LAN is being used, and the SQE bit is not turned on in the external transceiver box. Xstation 120 LAN statistics screen indicates bootp packets being sent out, but none being received (first group of four numbers incrementing, second group remains all zeroes, and fourth group count is one less than first group). 7) Determine whether the bootpd process is running by entering "ps -ae". Scan the list for a process named "bootpd". If bootpd is not on the list, go to step 12. 8) If bootpd is on the list (i.e., running), then check the date by entering "date". If the date isn't current, change it to the present date by entering "date MMDDHHMMYY", where MM is the two digit representation of the current month, and so on. 9) Enter "touch /etc/bootptab". 10) The next time the Xstation 120 sends out a bootp packet(first group of numbers increments), the bootpd process should start up again and send a response (second group of numbers increments). If no bootp reply packet is received at the Xstation 120, check /etc/bootptab and verify that the terminal is listed. If not, configure the Xstation on the network (see configuration chapter). 11) If there is still no reply at the Xstation 120 terminal, start up the bootpd process in the debug mode using the procedure described in step 14. 12) If bootpd is not on the list, check for the "inetd" process. If inetd is not running, start it up.](This is usually done by executing the /etc/rc.tcpip shell script. Make sure the script adequately represents the configuration of the host.) 13) If inetd is running and bootpd is not, check the /etc/inetd.conf file for an entry beginning with "bootps". If the entry is there, enter "/usr/bin/inetimp", then "ps -ae". Record the process number associated with the inetd process. Enter "kill -1 inetd_proc_number", where inetd_proc_number is the number obtained from the process list. Wait until the Xstation 120 terminal sends out another boot request then enter "ps -ae" and check the list for the bootpd process. 14) If the bootpd process is still not running, attempt to start it from the command line. Place a "#" before the "bootps" entry in the /etc/inetd.conf file. Enter "/usr/bin/inetimp". Enter "kill -1 inetd_proc_number". Enter "bootpd -d -d -d -d -s &". The bootpd process should start up, and various debug messages should be displayed. If the process does not start, enter "ls -l /etc/bootpd" and check the permissions. The permissions should be -rwxr-xr-x. Use the chmod command to set the permissions to 755. 15) If the process does not start, reinstall the Xstation Manager program. If it does, there is a problem with the inetd-bootpd interface, which is probably best fixed by killing the inetd process and starting it again. However, a simple work-around is to kill the bootp process ("kill bootpd_proc_number") and start it up from the command line without debug messages by entering "bootpd -s &". Xstation 120 LAN statistics screen indicates bootp packets being sent out and received successfully (first and second groups of four numbers increment together), but TFTP packet counts are slow and eventually time out. 16) Check the "tftp" entry in the /etc/inetd.conf file. Verify that it is uncommented. Check that a "nobody" account exists. 17) If numerous errors from inetd complaining of TFTP problems appear on the console, reload TCP/IP. If that doesn't work, reload AIX 3.1. Xstation 120 TFTP works (first two TFTP counters increment quickly to approximately 250), but various error messages are displayed on the Xstation 120 terminal (Cannot connect to fileserver, Could not read configuration file, Cannot load X server). 18) If the Xstation 120 couldn't connect to the fileserver, enter "ps -ae" and check the list for the x_st_mgrd process. If it is not there, start it from the command line by entering "/usr/lpp/x_st_mgr/bin/x_st_mgrd -b /usr/lpp/x_st_mgr/bin/x_st_mgrd.cf -s x_st_mgrd &". 19) If the x_st_mgrd process is there, check the /etc/services file and verify that x_st_mgrd is assigned a port (should be 7000). If it is not, add the process and port number to the /etc/services file, kill the x_st_mgrd process, and restart it as in step 18. 20) If the port number is there, check the /etc/bootptab file. At the end of the lines beginning "x_st_mgr", verify that "T170=1b58" appears. If not, add it, turn off the Xstation 120, and turn it back on. 21) If the Xstation 120 displays "Could not read configuration file" or "Could not load X server", enter "cd /usr/lpp/x_st_mgr/bin", and then enter "ls -l *". Check to make sure that the bootfile, bootfile.cf and x11xor.out files are "public readable" (e.g., the entry for the x11xor.out file should read "-rw-r--r-- 1 root ...etc..", where the third "r" represents the public read access enable bit). If not, use the chmod command to set the permissions to 644. Xstation 120 boots, but screen appears bright white. 22) This occurs when the rgb.txt file is not sent down from the host. Enter "cd /usr/lpp/x_st_mgr/bin", then enter "ls -l rgb.txt". The public read access bit should be set (the entry for rgb.txt should read "-rw-r--r-- 1 root ...etc..", where the third "r" represents the public read access enable bit). If not, enter "chmod 644 rgb.txt". Reboot the Xstation 120. 23) If the file is not found using the "ls -l" command, enter "find / -name rgb.txt -print", then change to the directory where the file is found and copy the rgb.txt file to the /usr/lpp/x_st_mgr/bin directory. Enter "cd /usr/lpp/x_st_mgr/bin". Enter "chmod 644 rgb.txt". Reboot the Xstation 120. Failures Displaying xterms 24) If you can display xterms at the local HFT, you should be able to display them on the Xstation 120. If you can't display xterms on the local HFT, you won't be able to display them at the Xstation 120. Xstation 120 boots, background map (grey cross-hatch) and small "x" cursor displayed, but no xterms displayed. 25) Ensure that the keymap file is compiled for X11. 26) Add a -fn option to the aixterm command found in the /usr/lpp/x_st_mgr/bin/x_st_mgrd.cf file (e.g. /usr/bin/X11/aixterm -fn Rom22 -W -e /usr/lpp/x_st_mgr/bin/login, where -fn Rom22 indicates that the Rom22 font is the default). Ensure that aixterm is in the /usr/bin/X11 directory. If not, enter "ln /usr/bin/X11/xterm /usr/bin/aixterm". Hello, this is AIXTIPS NEWS, an additional service from the AIXTIPS group. From now on when ever we feel there is some information that you need immediate, we will send it out as AIXTIPS NEWS. This file will not be cumulative, you have to save it somewhere before you receive a new one. But we will also maintain a AIXTIPS NEWSLOG file for those who join the service later. Get the newslog with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWSLOG BEWARE! Some of the information presented in here is confidential! #################################################################### 90.10.11 Table of contents: 1. X.25 Support in Germany for the /6000 2. Device driver for OEM Worm drives 3. How to generate Boot Floppies from a preloaded system 4. How to generate a install tape 5. SNA profiles samples 6. Limitations on the SSI Express 3270 Version =========================================================================== 1. X.25 Support in Germany for the /6000 From the German porting center: AIX v3 does not provide X.25 PAD support. (X.3, X.29, X.28) Harald Schneider (SCHNEIH at MUNIVM4) has a beta version of Hugbunadur HBX-PAD for IBM RISC System/6000 It is installed in the porting center for demos and tests. Features: - Connection to other Systems using X.25 PAD (also OEM) - Filetransfer from and to remote terminals and PC's - Login from ASYNC terminals vi phone line and X.25 PAD =========================================================================== 2. Device driver for OEM Worm drives The device driver for the Optimem 2.4 Gb and 4.4 Gb WORM drives is ready! If you need it this month (October), contact: Christopher D. Johnson Sun Coast SoftWorks, Inc. 1814 Arbor Drive South Palm Harbor, FL 34683 Chris' office phone is (813) 784-0072. There is a possibility that another party will buy/distribute this device driver in the future. To reach Optimem in Mountain View, CA, call (415) 961-1800. Also under development: device drivers for WORM drives from Laser Magnetic Storage Intl. Co. (LMS), Colorado Springs, CO, a subsidiary of Phillips. Specifically, the LD 4100 (5.6 Gb, 12") and the LD 510 (640 Mb, 5 1/4"). =========================================================================== 3. How to generate Boot Floppies from a preloaded system This script will create the 3 diskettes necessary to boot a RISC System 6000. These diskettes can be created from any installed (AIX V3.1) system. ------------------------------cut here--------------------------------------- # This shell script will create the 3 diskettes needed to boot # AIX V3.1 on the RISC System/6000. They are; # # 1. The boot diskette # 2. The display diskette # 3. The install diskette # # Created ITSC/Austin 07/13/90 RWR/CV # check to see if user has root permissions chmod u+x /usr/bin/bosboot > /dev/null 2>&1 # exit if permissions are incorrect if [ $? -ne 0 ] then echo "you must have root permissions to run this command" exit 1 fi format /dev/rfd0 # make boot diskette echo "making boot diskette ...................." /usr/bin/bosboot -w -c -p /usr/bin/dskt.proto -f /tmp/boot.fs -d /dev/fd0 format /dev/rfd0 # make display diskette echo "making display diskette ...................." /usr/lpp/bosinst/display/mkdispdskt format /dev/rfd0 # make install diskette echo "making install diskette ...................." /usr/lpp/bosinst/diskette/mkinstdskt --------------------------------------------------------------------------- Robert Ryan ITSC/Austin TL 793-5741 =========================================================================== 4. How to generate a install tape Now that you generated boot floppies with item 3, how do you create a installable backup tape? This process takes care only of the rottvg. User defined logical volumes are your own bussines! Use the command 'mkszfile' to generate the file /.fs.size . This file stores the layout of the rootvg. With the command 'mksysb /dev/rmt0' you create an installable tape that can be used with the above mentioned diskettes to reinstall or clone a machine. =========================================================================== 5. SNA profiles samples Subject: AIX SNA Services DEFAULT/sample profiles This Flash was prepared by AWD to give some guidance on SNA on RISC/6000. It is planned that further guidance will be provided in due course Tom Aspinall , ITSC Austin 4th Oct 1990 When AIX SNA Services is intalled on a machine, a DEFAULT set of profiles is created in the '/usr/lpp/sna/objrepos' directory. These profiles can be viewed via SMIT. They are intended to serve as models for creating new profiles. The procedure is to copy the existing DEFAULT profile, making modifications as necessary. Another source of information can be found in the '/usr/lpp/sna/samples' directory. This directory contains sample profiles for various types of connections (e.g. CICS, LU123, etc.) in files with a '.prof' suffix. These files are in stanza format, and can be loaded into the profile database via SMIT. They can then be modified to the specific requirements of the individual situation. Lastly, all of the profile types and their fields are defined in the "Customizing AIX SNA Services/6000" articles in the on-line pub. There is also a section called "Sample Profiles" that describes the profiles in the '/usr/lppp/sna/samples' directory. =========================================================================== 6. Limitations on the SSI Express 3270 Version IBM CONFIDENTIAL IMPORTANT LIMITATION on Systems Strategies Express 3270 Software There is an important LIMITATION that you should be aware of. The SSI 3270 (called Systems Strategies Express 3270) offering that IBM helps to market will NOT run concurrently with the IBM SNA Services/6000 LPP or the IBM Network Management/6000 LPP. According to SSI, the SSI microcode takes over ALL the multiprotocol adapters in the system. This means that if you are running the SSI code, you cannot run SNA Services/6000 on other Multiprotocol adapters that you may have. This means that you cannot run Network Management/6000 software. The result of all this is that a RISC/6000 that is being used as a sna gateway to a host system will NOT be able to concurrently send alerts to Netview or participate in host network management functions such as HCF and Netview Distribution Manager. Customers have been (incorrectly) told that SSI 3270 and IBM SNA Services/6000 will peacefully coexist on the same RISC/6000 system, although on two different Multiprotocol Adapters. (Information currently available on HONE/QUAT states this.) KEY POINTS: 1) Be aware of the limitation as it exists. 2) Review account configurations that you have sold the System Strategies Express 3270 software. SUPPORT: Systems Strategies Inc. (SSI) support is not provided by the ITSC. It is provided by SSI: in Europe through it's London office 81-568-9997 in the USA through it's New York office (212) 279-8400 For questions about this memo please enter them in QUAT/IQ/EQUAL. POSSIBLE "WORKAROUND": The following is a method to do 3270 SNA emulation with the SSI product and still be able to send alerts to a netview host (note that this will require TWO RISC/6000 machines): --------------------------------------------------- | 3270 sessions via SDLC line | | | | | ----------- ------------ ------------ | | | | | | |RISC/6000| |RISC/6000 |-------------------| Netview | | #1 | | #2 | SDLC line to host| Host | | | | | (for alerts) | | | | | | | | ----------- ------------ ------------ | | __|_____________________|____ Ethernet or Token Ring RISC/6000 #1 has -AIX 3.1 -Network Management/6000 (for sending alerts to RISC/6000 #2) -Systems Strategies Express 3270 (for 3270 emulation) RISC/6000 #2 has -AIX 3.1 -Network Management/6000 (to receive alerts from RISC/6000#1 and forward them to the Netview host) -SNA Services/6000 (for establishing a SSCP-PU session with the Netview host) In this setup, you can run your 3270 sessions on #1. RISC/6000 #2 is the "Collection Point" for the alerts that are generated by #1. (The Risc/6000 #1 is an "Entry Point" for alerts.) In this manner, all alerts on the network can be forwarded to a Netview host. ======================================================================== 90.10.22 Table of contents: 1. Fortran tuning for the /6000 with up to 50MFLOPs!!!!! 2. How to print transparently ASCII on PostScript printer 3. Making specific changes for AIXterm keyboards Mapping the Backspace keys 4. How do you define a new termmap for ODM/SMIT? 5. A smarter way to log out of the X-station =========================================================================== 1. Fortran tuning for the /6000 with up to 50MFLOPs!!!!! RISC System/6000 FORTRAN Programs Can Approach 50 MFLOPS (Now available to customers as a "G" publication) A RISC System/6000 tuning guide is now available that shows programs can approach up to 50 Mflop instructions versus the normal 10 Mflops expected. This publication is available from local IBM Marketing Representatives as GG24-3611 enti- tled "IBM RISC System/6000 Performance Tuning for Numer- ically Intensive FORTRAN and C Programs." The intended readers are programmers involved with numer- ically intensive computing (NIC) and are concerned with benchmarking and porting NIC applications to the IBM RISC System/6000. NIC programs are predominantly FORTRAN and most of the examples are in FORTRAN. C Language can also be used and can yield the same improvements. The highest exam- ple in the guide is about 46 Mflops. Some of the techniques involve undocumented and unsupported compiler options. These are "Clearly Differentiated Pro- gramming Interfaces" per the IBM "Requirements and Guide- lines for Clearly Differentiated Programming Interfaces" ZZ28-7013. Typical floating point intensive FORTRAN and C programs will perform at about 10 Mflops on a 25MHz IBM RISC System/6000 Model 530 with the IBM XL FORTRAN and C compilers and no change to the source code. The hardware is, however, capa- ble of a peak rate of up to 50 Mflops. Speeds approaching this can be achieved with programs written in standard FOR- TRAN or C Language without the need for special assembler programming techniques. Using these techniques, triple- nested loop algorithmic constructs such as matrix multiply can be programmed to approach peak rates. This guide was written by Dr. Ron A. Bell of IBM United King- dom, Ltd. Dr. Bell is with the IBM Technical and Supercom- puting Centre of Competence (TSCC), in Chiswick, England. Softcopy of the guide can be obtained by sending a PROFS NOTE to Milton Thrasher of IBM AIX Systems Marketing on RHQVM01(MTHRASH). ========================================================================== 2. How to print transparently ASCII on PostScript printer Subject: A Generic transparent Postscript/ASCII Software Switch Warning: Long Append The following is a HOWTO procedure for setting up a transparent Postscript/ASCII Software switch for native postscript printers. This allows programs like "InfoExplorer" to "Print Article" without manual reset by user(s). The procedure was given to me by an IBM Business Partner, Phil Houtz of "Fulcrum" a Computer Consulting Service, located in Albuquerque, New Mexico. Phil is owner of the firm and my personal friend. I have no financial stake in Phil's company. He and I share many RT and presently RISC System/6000 trials and tribulations. More importantly, we have also enjoyed numerous pitchers of Killian's Red over pool. He does not have any concern over my posting this to our (IBM's) forums. NOTE: Some printers may allow for a software select of HP Laserjet or ASCII output. Unless a time delay (common) is needed before transmission of text, put the "select emulation" string in the printer attributes "ci" variable via SMIT virtual printers support. End emulation with the "end" string in the "cr" variable. Emulation switching time delays, etc., will usually render this infeasible. Similarly, printers like the IBM 4019 will be unable to be software switched. In those cases, use the following to effect software emulation to translate ASCII to Postscript. The User should set up a queue, perhaps default, which tells the printer to translate ASCII to PostScript. Here follows a procedure: 1) Create two virtual PostScript printers against the same physical printer. If it's a non-IBM printer, pick something similar from one of the IBM definitions, e.g. 4216-31. 2) Create a PostScript emulator via PostScript commands in a file. Place the files in /usr/bin so that everyone can find them. The following Postscript code is taken from a PostScript manual, PostScript Adobe 2.0 to be precise. This code contains a very important component to most PostScript printers, the "%%" commands (minus the quotes). This code does not execute properly without them. Instances of "%some words" are comments. By comparison, "%%EndProlog", is a command. ---------------- FILENAME: /usr/bin/psprint.ps ----------------------- %! %%Title: ASCII printer emulator /buff 5000 string def /leftmargin 72 def /topmargin 72 def /bottom 72 def /top 792 topmargin sub def /ptsize 10 def /lead 10 def /EOLchar (\n) def % line feed /F {findfont exch scalefont setfont} bind def /newline { %def currentpoint exch pop lead sub dup bottom lt { %if showpage pop top } if leftmargin exch moveto } bind def /emulate { %def { %loop currentfile buff readstring exch EOLchar { %loop (innermost) search { %ifelse show newline }{ %else show exit } ifelse } loop not { %if readstring found EOF exit } if } loop showpage leftmargin top moveto } bind def %%EndProlog %%BeginSetup ptsize /Courier F leftmargin top moveto %%EndSetup emulate 3) Create an "end of file" character file. ---------------- FILENAME: /usr/bin/CtrlD ----------------------------- echo `\004` >/usr/bin/CtrlD or echo `\020\004` >/usr/bin/CtrlD Some printers "see" 020 pluss 004 better than just 004. 4) Create an executable script to catenate three files together and pipe them to the "real" Posctscript print queue. The three files which will be catenated are: a) the emulator file b) file to print c) "end of file" ---------------- FILENAME: /usr/bin/psscript -------------------------- cat /usr/bin/psprint.ps $1 /usr/bin/CtrlD enq -P ps:lp0 In this example, "psprint yourfiletoprint" should execute and result in a printout of your print file. If not something is wrong in the preceding. 5) Modify /usr/lpd/qconfig stanza, "backend = ", on ASCII printer definition. (Yes, this is also called "/etc/qconfig", but we've experienced problems with INed erasing linked references. So, either use the "real" filename or perhaps vi.) ---------------- FILENAME: /usr/lpd/qconfig --------------------------- * ASCII queue ascps: device = lp0 lp0: file = /dev/lp0 header = never trailer = never access = both backend = /bin/sh /usr/bin/psprint * PostScript queue ps: device = lp0 lp0: file = /dev/lp0 header = never trailer = never access = both backend = /usr/lpd/piobe 7) Use "Print Article" from "InfoExplorer" or any other print-from-program. You're done. ASCII is now the default and you can always print PostScript simply by selecting the "ps" queue. Obviously, there is no requirement to use ASCII print as the default. Try "InfoExplorer" prints without it, though. (Default printer is "topmost" definition in the "qconfig" file.) By the way, the above actually worked on a QMS PS810 Turbo printer. Art Cannon ACANNON at DALVMIC3 ========================================================================== 3. Making specific changes for AIXterm keyboards Mapping the Backspace keys I found the foolowing on a USNET forum and I think for some weird X keyboard mapping problems this is a pointer to the solution: I got the AIX xterm to generate a DEL instead of ESC [ P (and make the tty driver use it as my delete character) using the following two files. I set the environment variable XENVIRONMENT to the value $HOME/.Xresources.aix so only programs running on the AIX machine get these resources. The resources set the xterm terminal modes to use Delete instead of Backspace, and (within xterm only) remaps the keysym ``Delete'' to insert what you normally expece the Delete key to insert -- ASCII code 127 (decimal). The second file, .Xmodmap.aix, makes the BackSpace and Delete keys equivalent. It also swaps the Control and Caps Lock keys, so I end up with a keyboard that doesn't make me want to break it into little pieces after 5 minutes' use. I put the following line in my .xinitrc to make the keymap change: xmodmap .Xresources.aix Those who think BackSpace is the right way to delete backwards, and the Control key is less important than Caps Lock, will probably not find these changes of much use. If you're using an RS/6000 in a Sun or DEC environment, though, they may help. =---------------------------- .Xresources.aix ------------------------------- - ! ! Makes sure I get a DEL when you type a BackSpace on an aixterm ! window, and sets up the default TTY modes to match. ! ! This is in a OS/CPU-specific resource file because R4 xterms complain ! if I use XTerm*Translations to set the translations (because only the ! VT100 and Tek4014 widgets know about the string() method). If I use ! XTerm*.VT100.Translations or something similar, aixterm doesn't understand. ! XTerm.ttyModes: erase ^? kill ^u intr^c XTerm.Translations: #override \ Delete: string(0x7f)\n\ Meta Delete: string(0x1b) string(0xff) =---------------------------- .xmodmap.aix ---------------------------------- - ! ! Swap Caps_Lock and Control_L on an RS/6000 keyboard. ! remove Lock = Caps_Lock remove Control = Control_L keysym Control_L = Caps_Lock keysym Caps_Lock = Control_L add Lock = Caps_Lock add Control = Control_L ! ! Make Delete and BackSpace have the same name ! keysym BackSpace = Delete =---------------------------Cut and serve ---------------------------------- -- Mic Kaczmarczik gripe@{emx,ix1,ccwf} (Unix consulting, 1-025 1) Unix / VMS / Cyber Services ...!cs.utexas.edu!ut-emx!mic (UUC P) UT Austin Computation Center mic@emx.utexas.edu (Interne t) mic@utaivc (BITNE T) ========================================================================== 4. How do you define a new termmap for ODM/SMIT? If you have a strange Terminal that needs a termmap file that is not included with the system, this is what to do: If you create your own new termmap in the directory /etc/nls/termmap you will have problems to add it to the system. If you don't want to use just setmaps but also the chdev command or smit you have to tell ODM about the new termmap. Use the following procedure: Create an ascii file for example /tmp/dummy.odm with the following entries PdAt: (it is the ObjectClass in ODM) values = "none,vt220,ibm3161-C,volker" (volker is a new termmap. It is important, that you type all the values, and not only the new one) After creating this file, you have to run the following 2 commands odmchange -o PdAt -q "attributes = 'omap'" /tmp/dummy.odm odmchange -o PdAt -q "attributes = 'imap'" /tmp/dummy.odm With these commands you change the ODM entry, and add your new own termmap to the system, so you can use either chdev or change tty in smit, to make the new termmap for your terminal available. After this you can remove the file /tmp/dummy.odm Volker Kuhm ========================================================================== 5. A smarter way to log out of the X-station: My goal was to create a single command that would log you off from an Xstation from any window and kill anything of yours that was still running. What I don't like: - Ctrl-D because you have to go to each window and hit Ctrl-D. Too many steps! - Go to login window and hit Ctrl-D. I hate this because it kills mwm and leaves all child windows running without mwm! - Kill -15 -1 I hate this because it kills mwm and leaves all windows running without mwm! - Kill `ps -u $LOGNAME|grep 'X$'|awk '{ print $1 } '` When running mwm on an Xstation it doesn't do any good to kill a process starting with X (there aren't any!). This may work ok when logged in on the console. I have only tried it on an Xstation. What works: The following korn shell script will check if your userid is root or if you are not logged in on an Xstation. If you're userid is root and you do a kill -9 -1 you will have to reboot the machine! It will kill all jobs running at root! If you are at the console and you run kill -9 -1 you will have to reboot the machine unless you can figure out how to restart the console from another terminal. (This was tested on a 6090 attached console I don't know about ascii consoles etc.) The following script is a clean way of killing everything on an Xstation with one command. We have named it bye and put it in /bin for everyone to use. #!/bin/ksh # bye # a command to log off an Xstation # written by Gerald Pattyn 10-3-90 # # strip away everything except what is inside 1st ()'s from id call # to extract userid # user=$(expr "$(id)" : '.*(\([0-z]*\).* ') # # do not exec kill if root or if not on an Xstation # the env var XSTATION is undefined if not on an Xstation # if [[ $user != "root" && -n "$XSTATION" ]] then kill -9 -1 else if [[ $user != "root" ]] then print $0 can only be run from an Xstation else print user id is $user - $0 cannot be run by $user \(kills all processes\) fi fi Note: the else print.... line was split to fit in this append. [ is is open square bracket ] is is close square bracket Gerald Pattyn Federal Systems Integration, Boulder ========================================================================== The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offense. -- E. W. Dijkstra #################################################################### 90.11.14 Table of contents: 1. AIX v3 RAM & DASD requirements 2. XLC compiler dd23 option is NOT documented. 3. AIX v3 Date error 4. How to set up Printers for the X-station 5. Recomended AIX Standard Literature: =========================================================================== 1. AIX v3 RAM & DASD requirements The requirements for memory and disk space for AIX V3, and associated LPPs, have been revised by AWD Development. The new requirements have been put into the OLSS (QUAT) and SETI databases and can be found by searching on RISCSYSTEM RAMDASD. These figures relate to the GA level code and have not yet been revised for any subsequent PTF. Please ensure that the new figures are used for all situations. Any queries about this should be made using QUAT. =========================================================================== 2. XLC compiler dd23 option is NOT documented. **** The following information has been provided by AWD *** Subject: Software &/or Documentation errors associated with RISC/6000 pre-GA Hardware systems Attention All Marketing Support and Vendor Support Personnel: XLC compiler dd23 option is NOT documented. =========================================== There are two related options available on the XLC compiler, dd23 and dd24. Of these, only the dd24 option is officially documented in the referenced publications and files: - XLC User's Gd, Chapter 4, section on "Compiler Options". - XLC User's Gd, Appendix A, "Single Precision Fl Pt Overflow". - In the file /usr/lpp/xlc/bin/README.xlc - XLF User's Gd, Chapter 3, section on "Compiler Options". - XLF User's Gd, Appendix F, "Single Precision Fl Pt Overflow". - In the file /usr/lpp/xlf/DOC/README.xlf The dd23 option was not documented because it was decided that because planars with the FPU level 2.3 would not be shipped as GA hardware and the loaner machines with these level chips would be quickly upgraded to GA level, it would not be necessary to document it in the pubs. It was left t o organizations supporting the ESP machines to notify those users of the 'work-around' as needed. The dd24 option was documented because it was believed that, due to the large number of FPU 2.4 level chips already manufactured, they would be shipped in GA-level hardware. The dd23 and dd24 options do NOT have overlapping function. Use of the dd24 option DOES NOT get fixes implemented for the dd23 problem. The dd24 option fix is ONLY specific to the FPU 2.4 level chips and has NO effect on the problem specific to the FPU 2.3 level chips. Description of the problem specifics follows: Pre-GA CPU Planar Board Floating Point Problem There is a potential floating point problem on some of the pre-general availability (pre-GA) RISC System/6000 machines. The information that foll o is how to identify the pre-GA machines and gives some alternative actions t handle the situation. One version of the pre-GA planar board for the RISC System/6000 can someti m produce wrong answers during floating point calculations. This situation o n occurs if the program was compiled with the optimization flag turned on. T h wrong answers may not be readily obvious. The early CPU planar board with t problem is the 2.3 level board. This problem was remedied prior to general shipment of the RISC System/6000 to customers. However, there are a number early systems with the 2.3 level board which were shipped to IBM sites (e. g IBM branch and area offices), to a number independent software developers f porting work and to selected customers for early evaluation. The 2.3 level board can be identified by a part number on the CPU planar board. To see the part number, power off the system. Remove the front cove r the machine and then the left side cover. Face the left side of the machin e The part number is printed in black on a dark gold tag. The tag is on the board surface where slot B for memory cards is located. The memory card sl o are located in the upper right section of the machine. If slot B has a mem o card installed, it may have to be removed to see the tag. The 2.3 level pa r numbers are: 320 CPU 2.3 board 59f3594 59f3597 70f9650 520 CPU 2.3 board 59f3591 530/730 CPU 2.3 board 59f3583 59f4403 The circumstances that provoke the problem are not readily evident when looking at user source code. The technical explanation would be of little u to vendors and customers. Programs that produce erroneous data when compil e optimized versus not optimized are good candidates for the use of the corrective action described below. It is important to note that any program that tests good on a machine with 2.3 CPU board will work on any machine available. Programs tested on GA hardware might not work on pre-GA hardware. Testing on pre-GA hardware wou l be required to verify this. Over time, all pre-GA machines will be upgrade d GA level. For a specific machine, use the above part numbers to verify if the machin e being used has a 2.3 level CPU board. If it does not, there is no problem. Should corrective action be required, there are two alternatives to handle this situation: 1. The preferred solution is to re-compile the programs with a compiler fl a which generates code that bypasses the problem. The performance impact is within one percent. Programs compiled with this flag will run on the pre-G A well as the GA machines. The compiler flag is: -q xflag=dd23 Note: This flag is not documented in the compiler publications. 2. Another solution is to re-compile without optimization. This could resu l in significant performance loss depending on the amount of optimization achieved by the compiler. Any question related to the previous item should be submitted through QUAT =========================================================================== 3. AIX v3 Date error (a bit late, but better a late explanation than a endless problem. afx) Subject: date/time calculation error *** Notice *** Any customers with RISC System/6000 systems running AIX Version 3.1 without Corrective Service 3001 (July Update) may experience a problem with the system date and time between October 27 and November 2. The problem, which was a bug in computing the Julian calendar day, is corrected by Corrective Service 3001 and any subsequent cumulative update (such as 3002). If your customer does not have the update, he can be instructed to use the "date" command to reset the system date and time. However, he should be made aware that it will be necessary to manually reset the date each time he reboots until after November 2. After November 2, the date will again be calculated correctly until next July. If the customer does not reboot between October 27 and November 2, he will not see the problem. To confirm your installed software release, enter the following command: lslpp -h bos.obj The output will be a table similar to the following: Option Name State Event Date/Time Release UserName ----------- ----- ----- --------- ------- -------- bos.obj Active Commit MM/DD/YY 03.01.0000.xxxx root The significant digits in the Release column which indicate GA level of software are: 03.01.0000.xxxx (disregard the xxxx) If 3001 has been installed on the system, the release will be: 03.01.0001.xxxx =========================================================================== 4. How to set up Printers for the X-station Subject: Multiple Virtual Printers on Xstation It works! I set up the queues so that I can print both ascii and postscript on the 4216 attached to the workstation. Just rmvirprt mkque -q alps mkquedev -q alps -d dalsh -a 'file = /dev/null' -a 'backend = /usr/lpp/x_st_mgr/bin/lpx alshome' mkvirprt -t 4216-31 -sps -q alps -d dalsh -n alshome mkque -q alas mkquedev -q alas -d dalsh -a 'file = /dev/null' -a 'backend = /usr/lpp/x_st_mgr/bin/lpx alshome' mkvirprt -t 4216-31 -sasc -q alas -d dalsh -n alshome Then you simply enq -Palps for a postscript file and enq -Palas for a ascii file. alas = queue name for ascii printing alps = queue name for postscript printing dalsh = device name associated with BOTH queues alshome = Xstation node name 4216-31 = printer type -sps = setting for postscript virtual printer -sasc = setting for IBM extended ASCII virtual printer You can add additional queues and virtual printers if you want DIABLO or HP Laserjet emulation. Have fun! Allan D. Griefer, IBM Almaden Research Center, San Jose, CA VNET/BITNET: GRIEFER at ALMADEN Internet: grieferibm.com UUCP: ...uunetibmarcgriefer mcimail: 398-8024 ========================================================================== 5. Recomended AIX Standard Literature: SC23-2195 IBM RISC System/6000 Quick Start Kit GK2T-0237 IBM RISC System/6000 General Information and Planning Information K it SA23-2646 IBM RISC System/6000 HW Technical Reference Options and Devices SC23-2201 Task Index and Glossary for IBM RISC System/6000 SC23-2199 AIX Commands Reference for IBM RISC System/6000 SC23-2202 AIX General Concepts and Procedures for IBM RISC System/6000 SC23-2203 AIX Communication Concepts and Procedures for IBM RISC System/6000 SC23-2204 IBM RISC System/6000 Problem Solving Guide SC23-2205 AIX General Programming Concepts for IBM RISC System/6000 SC23-2212 AIX Editing Concepts and Procedures for IBM RISC System/6000 SC23-2264 AIX Xstation Manager/6000 System Administrator's Guide SC09-1259 XL C User's Guide for IBM AIX Version 3 for RISC System/6000 SC09-1260 XL C Language Reference for IBM AIX Version 3 for RISC System/6000 GG24-3381 AIX Communications Handbook (NB this Redbook is for the RT, not RS6 K) GG24-3489 AIX Distributed Environments ( NFS, NCS,...) GG24-3589 AIX National Language Support Guide ========================================================================== Maintainer's Motto: If we can't fix it, it ain't broke. Hello, this is AIXTIPS NEWS, an additional service from the AIXTIPS group. From now on when ever we feel there is some information that you need immediate, we will send it out as AIXTIPS NEWS. This file will not be cumulative, you have to save it somewhere before you receive a new one. But we will also maintain a AIXTIPS NEWSLOG file for those who join the service later. Get the newslog with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWSLOG If you got this file as a copy and want to have any future versions sent to your reader automatically use the command: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC SUB AIXTIPS NEWS BEWARE! This file has to be treated as IBM CONFIDENTIAL! have fun AIXTIPS at MUNIVM4 #################################################################### 90.11.26 Table of contents: 1. WORM Drive Support for the /6000 2. Bug fix for Interleaf on the monochrome card 3. AIXTIPS Release 1.2 will be ready by the first of december. 4. INFOEXPLORER CD ROM PUBLICATIONS 5. AIX PS/2 1.2 DOCUMENTATION ERROR 6. RISC SYSTEM/6000 MAKEFILES FOR SPEC 7. RISC SYSTEM/6000 PERFORMANCE MONITORING AND TUNING GUIDE 8. RISC SYSTEM/6000 CAD/CAM THROUGHPUT BENCHMARK RESULTS 9. How to handle a storage constraint Modell 320 10. Handling the uname bug (wrong serial numbers reported) 11. Basic AIX 3 Documentation =========================================================================== 1. WORM Drive Support for the /6000 There is a company that has WORM drive support for the /6000. TenX Technology 4807 Spicewood Springs Rd., Bldg. 3 Austin, TX 78759 (800) 922-9050 or (512)346-8360 Fax : (512)346-9580 TenX Has worm drives and a controller unit which makes WORMS appear to be standard SCSI hard drives. The offer capacities ranging from 600MB up to 6GB. =========================================================================== 2. Bug fix for Interleaf on the monochrome card There is a bug fix neccesary if you want to run Interleaf on a /6000 with the monochrome adapter. Get it from your country defect support center. The APAR number is IX13578 =========================================================================== 3. AIXTIPS Release 1.2 will be ready by the first of december. It will contain 14 new tips, some of them you may have seen allready in AIXTIPS NEWS. It will also contain an ASCII/EBCDIC version for those that want to view it online but have no TeX preview capability. Get it with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS PACKAGE You will find further instructions about printer specific files in there. =========================================================================== 4. INFOEXPLORER CD ROM PUBLICATIONS Some manuals listed in the Documentation and Training Offerings Overview (GC23-2192) as being included on the CD ROM Hypertext Information Base Library were in fact not included. The following manuals are not on the CD ROM: IBM RISC System/6000 POWERstation and POWERserver Hardware Technical Reference -- General Information (SA23-2643) IBM RISC System/6000 Hardware Technical Reference -- 7012 POWERstation and POWERserver (SA23-2660) IBM RISC System/6000 Hardware Technical Reference -- 7013 and 7016 POWERstation and POWERserver (SA23-2644) IBM RISC System/6000 Hardware Technical Reference -- 7015 POWERserver (SA23-2660) IBM RISC System/6000 POWERstation and POWERserver Hardware Technical Reference -- Options and Devices (SA23-2646) These manuals will be included in the next release of the RISC System/6000 Hypertext Information Base Library CD currently scheduled for 4Q90. SLSS subscribers will automatically receive the new CD ROM. =========================================================================== 5. AIX PS/2 1.2 DOCUMENTATION ERROR Please be advised of the following: The AIX PS/2 Version 1.2 Operating System Commands Reference lists a -d and -c flag for the 'display' command. This is an error in the publica- tion. These flags are NOT supported. The user DOES NOT have the capability of changing the physical display used by the standard out terminal or changing the default display for subsequent opens to the specified display. Dual display functionality is not supported on AIX PS/2 1.2 =========================================================================== 6. RISC SYSTEM/6000 MAKEFILES FOR SPEC Suite 1.0 and Suite 1.1 IBM results for the SPEC Suite Release 1.0 Benchmark substantiate the superior performance of the RISC System/6000 in technical computing environments. For customers who have purchased the SPEC Benchmark Suite, and are attempting to duplicate IBM performance results, IBM specific makefiles can make the task much easier. Since the SPEC Suite Release 1.0 Benchmark tape was shipped before the announcement of the RISC System/6000, IBM specific makefiles are not available on the tape. Subsequent releases of the SPEC Suite will have IBM makefiles available. In the meantime, you can obtain the makefiles IBM used to obtain the official RISC System/6000 SPEC results from the Performance Evaluation Center Tools disk. These makefiles can be used with the SPEC Suite Release 1.0 and 1.1 Benchmarks. To obtain the makefiles, issue this command: TOOLS SENDTO DALVM41B TOOLS PEC GET SPECMF PACKAGE The README file which accompanies the PACKAGE explains how to download the makefiles to a RISC System/6000. =========================================================================== 7. RISC SYSTEM/6000 PERFORMANCE MONITORING AND TUNING GUIDE now available to the field. This document consolidates information relative to performance of the AIX RISC System/6000, which by nature spans various aspects of the system. The document serves as an introduction and guide to performance monitoring and tuning. It outlines steps that are useful for performance tuning and provides information on the implementation of various aspects of the system that are useful to understanding performance. Since the document was developed for distribution to customers, it references only tools and facilities that are shipped with the product. It serves as a valuable reference, describing these various tools in a single document. The document also provides information on system tuning techniques. The document, "RISC System/6000 Performance Monitoring and Tuning Guide" , is presently available internally as a "LIST3820" formatted script file. The file can be printed from VM on a 3820 printer using any of various VM print utilities (PPRINT, PUBS, DOCS, etc). It is temporarily classified "Internal Use Only". The document is being prepared for external release, and in the future, will be available through publications order. Presently the document may be obtained via a VM TOOLS request. To receive the document, from your VM account issue the command: TOOLS SENDTO DALVM41B TOOLS AIXIC GET 6KTUNING PACKAGE Since the file is large, the requestor should be aware that transmission of the file may be delayed by VNET. To subscribe to the package, from your VM account issue the command: TOOLS SENDTO DALVM41B TOOLS AIXIC SUBSCRIBE 6KTUNING PACKAGE You will be notified of any changes and will automatically receive the modifications. =========================================================================== 8. RISC SYSTEM/6000 CAD/CAM THROUGHPUT BENCHMARK RESULTS RISC System/6000 Shines in Throughput Benchmark A Series of Workstation Throughput Tests The Albert Consulting Group has completed its benchmark of eleven different workstations, four of which included different configurations of RISC System/6000s. Their benchmark is The Albert Group Interactive Throughput Tests or TAGITT and consists of a series of tests used to compare performance of workstations running CAD/CAM software. TAGITT reproduces an interactive user design session by replaying captured user keystrokes on each target machine. MCS Anvil software was used in these tests, since at test time that was the only software supported by all the workstations being tested. TAGITT/Anvil measures the machine response time component of a simulated three-day user session. The IBM workstations tested were RISC System/6000s, specifically the 540, 530, 530 Sabine, and the 320. Competitors workstations tested included two DECstation 5000s, the CX and the PX, a Silicon Graphics 4D/25 TG, a Tektronix XD88/20, a Data General AViiON, a HP 835 turbo SRX, and a Sun SPARCstation 330 CXP. The model 540 (configured as a workstation) is nearly twice as fast as the nearest competitor (DECstation 5000) and better than four times faster than the slowest machine tested (SPARCstation 330). The IBM 540 completed TAGITT/Anvil in less than 19 minutes. ALL CAD/CAM TESTS RISC System/6000 Model 540 |xxxxxxxxx RISC System/6000 Model 530 |xxxxxxxxxxx RISC System/6000 Model 530 3D |xxxxxxxxxxxxx RISC System/6000 Model 320 |xxxxxxxxxxxxxx DECStation 5000 CX |xxxxxxxxxxxxxxxxxx DECStation 5000 PX |xxxxxxxxxxxxxxxxxxxxx SGI 4D/25TG |xxxxxxxxxxxxxxxxxxxxxxx Tektronix XD88/20 |xxxxxxxxxxxxxxxxxxxxxxxxxxx Data General AViiON |xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx HP 835 Turbo SRX |xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Sun SPARCStation 330 CXP |xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |---------+---------+---------+---------+---- 0 1200 2400 3600 4800 Time to Complete (sec) ALL CAD/CAM TESTS by Discipline x Design RISC System/6000 Model 540 |xxxoo+*## o Drafting RISC System/6000 Model 530 |xxxxooo+*## + Numerical Control RISC System/6000 Model 530 3D |xxxxxooo+*### * Solid Modeling RISC System/6000 Model 320 |xxxxxxooo+*### # Large File Simulatio n DECStation 5000 CX |xxxxxxxooooo+*#### DECStation 5000 PX |xxxxxxxxxoooooo+*#### SGI 4D/25TG |xxxxxxxooooooo+*####### Tektronix XD88/20 |xxxxxxxxxxooooooooo++*##### Data General AViiON |xxxxxxxxxxxxoooooooooo++**###### HP 835 Turbo SRX |xxxxxxxxxxoooooooooooo++**###### Sun SPARCStation 330 CXP |xxxxxxxxxxxxxxxxoooooooooooooo**++####### |---------+---------+---------+---------+---- 0 1200 2400 3600 4800 Time to Complete (sec) DESIGN TASKS Discipline RISC System/6000 Model 540 |xxxxxxxxx RISC System/6000 Model 530 |xxxxxxxxxxx RISC System/6000 Model 530 3D |xxxxxxxxxxxxxx RISC System/6000 Model 320 |xxxxxxxxxxxxxxx DECStation 5000 CX |xxxxxxxxxxxxxxxxxx DECStation 5000 PX |xxxxxxxxxxxxxxxxxxxxxxx SGI 4D/25TG |xxxxxxxxxxxxxxxxxx Tektronix XD88/20 |xxxxxxxxxxxxxxxxxxxxxxxxxxx Data General AViiON |xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx HP 835 Turbo SRX |xxxxxxxxxxxxxxxxxxxxxxxxxxxx Sun SPARCStation 330 CXP |xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |---------+---------+---------+---------+---- - 0 450 900 1350 1800 Time to Complete (sec) DRAFTING TASKS Discipline RISC System/6000 Model 540 |ooooooo RISC System/6000 Model 530 |ooooooooo RISC System/6000 Model 530 3D |oooooooooo RISC System/6000 Model 320 |ooooooooooo DECStation 5000 CX |ooooooooooooooooo DECStation 5000 PX |ooooooooooooooooooo SGI 4D/25TG |ooooooooooooooooooooooo Tektronix XD88/20 |ooooooooooooooooooooooooooo Data General AViiON |oooooooooooooooooooooooooooooooo HP 835 Turbo SRX |ooooooooooooooooooooooooooooooooooo Sun SPARCStation 330 CXP |ooooooooooooooooooooooooooooooooooooooooo |---------+---------+---------+---------+---- - 0 400 800 1200 1600 Time to Complete (sec) NUMERICAL CONTROL TASKS Discipline RISC System/6000 Model 540 |++++++++++ RISC System/6000 Model 530 |++++++++++++ RISC System/6000 Model 530 3D |+++++++++++++++ RISC System/6000 Model 320 |+++++++++++++++ DECStation 5000 CX |++++++++++++++++++ DECStation 5000 PX |++++++++++++++++++++++++++ SGI 4D/25TG |+++++++++++++++++++++++ Tektronix XD88/20 |+++++++++++++++++++++++++ Data General AViiON |++++++++++++++++++++++++++++ HP 835 Turbo SRX |++++++++++++++++++++++++++++++++++ Sun SPARCStation 330 CXP |+++++++++++++++++++++++++++++++++ |---------+---------+---------+---------+---- - 0 45 90 135 180 Time to Complete (sec) SOLID MODELING TASKS Discipline RISC System/6000 Model 540 |******* RISC System/6000 Model 530 |******** RISC System/6000 Model 530 3D |********** RISC System/6000 Model 320 |*********** DECStation 5000 CX |*************** DECStation 5000 PX |**************** SGI 4D/25TG |******************* Tektronix XD88/20 |********************** Data General AViiON |****************************** HP 835 Turbo SRX |********************************* Sun SPARCStation 330 CXP |********************************** |---------+---------+---------+---------+---- - 0 40 80 120 160 Time to Complete (sec) LARGE FILE SIMULATION TASKS Discipline RISC System/6000 Model 540 |########## RISC System/6000 Model 530 |############ RISC System/6000 Model 530 3D |############ RISC System/6000 Model 320 |############### DECStation 5000 CX |################# DECStation 5000 PX |################## SGI 4D/25TG |############################## Tektronix XD88/20 |######################### Data General AViiON |############################** HP 835 Turbo SRX |############################## Sun SPARCStation 330 CXP |################################### |---------+---------+---------+---------+---- - 0 300 600 900 1200 Time to Complete (sec) ALL CAD/CAM TESTS by Function x Data Management RISC System/6000 Model 540 |x++++++** o User Interface RISC System/6000 Model 530 |x+++++++*** + Geometry RISC System/6000 Model 530 3D |x+++++++++*** * Graphics RISC System/6000 Model 320 |x+++++++++**** DECStation 5000 CX |xx++++++++++++**** DECStation 5000 PX |xx++++++++++++++***** SGI 4D/25TG |xx+++++++++++++++++**** Tektronix XD88/20 |xxo++++++++++++++++++****** Data General AViiON |xxo++++++++++++++++++++++******* HP 835 Turbo SRX |xxo+++++++++++++++++++++++++**** Sun SPARCStation 330 CXP |xxxo++++++++++++++++++++++++++++********* |---------+---------+---------+---------+---- 0 1200 2400 3600 4800 Time to Complete (sec) DATA MANAGEMENT Function RISC System/6000 Model 540 |xxxxxxxxxx RISC System/6000 Model 530 |xxxxxxxxxxxxx RISC System/6000 Model 530 3D |xxxxxxxxxxxxx RISC System/6000 Model 320 |xxxxxxxxxxxxxxx DECStation 5000 CX |xxxxxxxxxxxxxxxxxxxxx DECStation 5000 PX |xxxxxxxxxxxxxxxxxxxxxxx SGI 4D/25TG |xxxxxxxxxxxxxxxxxxxxxxxxxxx Tektronix XD88/20 |xxxxxxxxxxxxxxxxxxxxxxxxxxxxx Data General AViiON |xxxxxxxxxxxxxxxxxxxxxxxxxxxxx HP 835 Turbo SRX |xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Sun SPARCStation 330 CXP |xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |---------+---------+---------+---------+---- - 0 90 180 270 360 Time to Complete (sec) USER INTERFACE Function RISC System/6000 Model 540 |ooooooooo RISC System/6000 Model 530 |oooooooooo RISC System/6000 Model 530 3D |ooooooooooo RISC System/6000 Model 320 |ooooooooooooooo DECStation 5000 CX |oooooooooooooooo DECStation 5000 PX |ooooooooooooooooooo SGI 4D/25TG |ooooooooooooooooooooooooo Tektronix XD88/20 |ooooooooooooooooooooooooooo Data General AViiON |ooooooooooooooooooooooooooo HP 835 Turbo SRX |oooooooooooooooooooooooooooooooooo Sun SPARCStation 330 CXP |ooooooooooooooooooooooooooooooo |---------+---------+---------+---------+---- - 0 22.5 45 67.5 90 Time to Complete (sec) GEOMETRY Function RISC System/6000 Model 540 |++++++++ RISC System/6000 Model 530 |++++++++++ RISC System/6000 Model 530 3D |+++++++++++ RISC System/6000 Model 320 |++++++++++++ DECStation 5000 CX |++++++++++++++++ DECStation 5000 PX |+++++++++++++++++++ SGI 4D/25TG |+++++++++++++++++++++++ Tektronix XD88/20 |++++++++++++++++++++++++ Data General AViiON |+++++++++++++++++++++++++++++ HP 835 Turbo SRX |+++++++++++++++++++++++++++++++++ Sun SPARCStation 330 CXP |++++++++++++++++++++++++++++++++++++++ |---------+---------+---------+---------+---- - 0 900 1800 2700 3600 Time to Complete (sec) GRAPHICS Function RISC System/6000 Model 540 |********* RISC System/6000 Model 530 |*********** RISC System/6000 Model 530 3D |************ RISC System/6000 Model 320 |************** DECStation 5000 CX |**************** DECStation 5000 PX |****************** SGI 4D/25TG |**************** Tektronix XD88/20 |************************** Data General AViiON |*************************** HP 835 Turbo SRX |**************** Sun SPARCStation 330 CXP |************************************ |---------+---------+---------+---------+---- - 0 300 600 900 1200 Time to Complete (sec) For a hard copy report with better graphics, send a request to: CCCOMP at DFWVM03 =========================================================================== 9. How to handle a storage constraint Modell 320 There is a new version of the "Storage Requierements for IBM RISC System/6000" It is available in list3820 format from our tools disk: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET STORAGE LIST3820 It describes various ways of saving space on a 120Meg disk, how to live with only 8Mb of memory and what kind of performance you can expect. IT IS NOT MEANT AS A SELLING GUIDE FOR CRIPPLED SYSTEMS! It is meant to help reduce the damage allready done by selling such systems! =========================================================================== 10. Handling the uname bug (wrong serial numbers reported) There currently is a potential problem on ALL RS/6000 running G.A. and above code (no matter what update level you have applied). The problem exists with the uname in terms of being able to generate a unique identifier. Problem: Pre-G.A. machines had a 7 digit cpu id burned into ROM and post G.A. machines had an 8 digit cpu id burned into ROM. Kernel code (invoked by uname -m or uname system call) was written to accept 7 digits terminated with a 0xff. Thus the least significant digit from a 8 digit board is lost when a customer or program invokes uname. If a customer happens to have many machines of the same model group that just happen to have 8 digit serial numbers (post G.A.) in ROM that are all close to each other by serial number, it is possible that uname -m could return a 12 digit number that is non-unique. The layout of the 12 digits returned by uname -m is as follows: XXYYYYYYMMSS - where XX is always 00 - YYYYYY is the cpu idt - MM is the model number 31 = 320 14 = 540 30 = 520 02 = 930 10 = 530 & 730 - SS is submodel number which right now is always 00 EXAMPLE: If you do a lscfg -v pg on your machine you can see if you have a 7 or 8 digit cpu id (called processor identification). Thus if you had 6 model 320's and you did an lscfg -v and gathered all the processor id's: 00012841 00012844 00012842 00012845 00012843 00012846 This would tell you that this is a machine that had the 8 digit cpu id burned into ROM and if you were to do a uname -m on all 6 of these machines you would get 6 identical values which would be: 000012843100 After the uname fix is applied the number returned from uname -m will be: 0001284x3100 (where x will be 1-6 depending on which machine uname was issued) Thus, if a customer is trying to install a vendor application on these 6 machines there are two problems that can occur based upon how the vendor has implemented their licensing practice with uname. 1) The customer may be able to install a single license on multiple machines which would impact the vendor revenue. 2) The customer will only be able to install one license on one machine even though they purchased 6 licenses. (This is the more likely scenario) THE BIGGER PROBLEM: It is very possible that even though the customer has multiple RS/6000's that have a 8 digit cpu id, the serial numbers of those 8 digit id's are far enough apart that dropping the last digit still results in a unique cpu id and thus a unique uname -m return. In this case, all software is currently running without any problems. HOWEVER, when the customer applies the 3003 update which contains the uname fix and the ability to handle the 8th digit a new uname 12 digit number will be generated that will different than the "original" 12 digit number. If the vendor's licensing policy checks the uname at boot up of that application or at random times (as most of them do) the application will think it is no longer running on the machine it was licensed to run on and will stop running. At this point, the vendor has to get involved and re-issue key numbers etc. If the vendor and customers choose to apply the fix now, then they can call the 800 NSD number and request the following emergency fix: "Emergency uname fix for APAR #IX13713 build 3002" Since the emergency fix is the entire kernel (/unix) it is critical for the vendor/customer to understand that they need to apply the 3002 update AND THEN apply this 3002 kernel fix. There also exists emergency fixes based on a 3001 kernel and 9021 kernel but we recommend that they not apply these because if someone applies the normal 3001 update against a 9021 "fixed" kernel or a normal 3002 update against a 3001 "fixed" kernel, it will wipe the fix out and the original 12 digit uname number could be generated again and thus any applications that are running that check to make sure the uname is the same will fail. It is important to understand that it is a 100% certainty that the uname number (12 digit number) will change when the fix is applied and will also change back if the fix is overwritten with a new kernel (update). The exception to this is that the 3003 update contains the kernel fix, so if you apply the fix now on a 3002 base, when you apply the 3003 update, the uname will be the same. Also, it is conceivable (assuming the vendor/customer know what they are doing) that if a vendor/customer is at 9021 and does not wish to jump to 3002, they could apply the 9021 uname fix, then at a later time apply the 3001 update FOLLOWED IMMEDIATELY by the 3001 fix, then at a later date apply the 3002 update FOLLOWED IMMEDIATELY by the 3002 fix and finally apply the 3003 update (which contains the fix). Gary Andrews AIX Vendor Porting Center 8-752-7281 DFWVM03(ANDREWS) =========================================================================== 11. Basic AIX 3 Documentation IBM RISC SYSTEM/6000: On-line information content for AIX When placing an order for an IBM RISC System/6000, it is important to note that the documentation supporting AIX Version 3 was designed to be delivered on-line and viewed using InfoExplorer. Even though AIX information is on-line, three hardcopy manuals are always shipped with the IBM RISC System/6000: the Problem Solving Guide, the Quick Start Kit, and the AIX Installation Guide. Detailed descriptions of these manuals are provided later in this file. Recent customer feedback shows that although viewing information on-line using InfoExplorer is being received favorably, many end users would like to also have some number of hardcopy manuals to meet their needs for information in printed form. Therefore, it is extremely important to provide customers who use the IBM RISC System/6000 the opportunity to optionally order manuals. The following is intended to assist you in determining what manuals to order when the customer also wants to receive the on-line information in hardcopy form. AIX on-line information can be broken down into 3 primary groupings of manuals: non-programming, programming, and AIXwindows programming. How the user intends to use the IBM RISC System/6000 will determine what manuals or groupings of manuals you should order. SBOF numbers are provided below to facilitate ordering complete subsets of the on-line information. Of course, individual manuals can also be ordered using the following information. The "Documentation and Training Offerings Overview" in the RISC System/6000 General Information And Planning Information Kit, GK2T-0237, more completely explains the documentation and training offerings. Note: SBOFS for FORTRAN and Pascal manuals are available. They are also included in this tip. Manuals shipped in hardcopy form with every IBM RISC SYSTEM/6000 > IBM RISC System/6000 Problem Solving Guide, SC23-2204, serves as the primary reference should a user encounter a problem with the system hardware or software that cannot be corrected by the normal message actions. This book provides the user with steps that may either return the system to a normal operating condition or give the user sufficient information to place a service call. > IBM RISC System/6000 Quick Start Guide, SC23-2195, provides a new IBM RISC System/6000 system user with information about how to perform common tasks, such as logging in and logging off and accessing online documentation. Topics include AIX Version 3 for RISC System/6000, InfoExplorer, System Management Interface Tool (SMIT), and InfoTrainer The guide can help familiarize beginners with the system and also serve as a quick reference for experienced users. > AIX Version 3 for IBM RISC System/6000 Installation Guide, SC23-2341, discusses various methods of installing and maintaining the operating system. It also covers how to start up a pre-installed system for the first time. One copy of the guide is provided with the operating system. AIX non-programming manuals: SBOF-1526 > AIX Commands Reference for IBM RISC System/6000, SC23-2199, provides reference information about commands and is written for end users, system managers and programmers. This set of books (3 volumes) contains examples and descriptions of the commands and their available flags. The command entries are arranged in alphabetical order. > AIX General Concepts and Procedures for IBM RISC System/6000, SC23-2202, serves as the main resource for end users and system managers once they progress beyond the basic information contained in the Quick Start Guide. This book contains conceptual and procedural information, with sufficient conceptual information for users to determine when it is appropriate to perform the procedures. The procedures are applicable to a variety of user interfaces. > AIX Editing Concepts and Procedures for IBM RISC System/6000, SC23-2212-0, describes some of the editors that are available for use with the RISC System/6000 system unit and includes suggestions of some effective uses of these editors (for example, to develop programs or to create and edit general text files). This book also contains procedural information for using particular functions provided with editors. > AIX Communication Concepts and Procedures for IBM RISC System/6000, SC23-2203, serves as the system manager and end user's main source book for procedures associated with using, managing, and customizing communications networks. This book contains information about many types of RISC System/6000 communications networks. > AIX Files Reference for IBM RISC System/6000, SC23-2200, provides reference information about file formats, special files, and information associated with files (including keyboard and character tables). This book is written for system managers and programmers. > Task Index and Glossary for IBM RISC System/6000, SC23-2201, contains three important elements of the RISC System/6000 system: 1) lists of RISC System/6000 tasks and where they are documented in the library, 2) an error message index, and 3) a glossary of technical terms and abbreviations used in the RISC System/6000 library. AIX programming manuals: SBOF-1527 > AIX Calls and Subroutines Reference for IBM RISC System/6000, SC23-2198, provides reference information about system calls, kernel extension calls, and subroutines. This set of books (6 volumes) is written for programmers. > AIX General Programming Concepts for IBM RISC System/6000, SC23-2205, serves as the programmer's main source book for learning about the operating system from a programming perspective. > AIX Communications Programming Concepts for IBM RISC System/6000, SC23-2206, serves as the main source book for information about the communications facilities from a programming perspective. > AIX Kernel Extensions and Device Support Programming Concepts for IBM RISC System/6000, SC23-2207, serves as the programmer's main source book for learning about the kernel extensions that enable programmers to address devices. > XL C Language Reference for IBM AIX Version 3 for RISC System/6000, SC09-1260, describes the syntax and semantics of the C programming language that is implemented by the IBM AIX Version 3 for RISC System/6000 licensed program. This book is written for users who have some knowledge of C language programming concepts and some experience in writing C programs. > XL C User's Guide for IBM AIX Version 3 for RISC System/6000, SC09-1259, explains how to develop and compile C language programs on an IBM RISC System/6000 system unit that has the IBM AIX Version 3 RISC System/6000 licensed program installed. > Assembler Language Reference for IBM AIX Version 3 for RISC System/6000, SC23-2197, describes the syntax and semantics of the assembler language that is implemented by the AIX for RISC System/6000 licensed program. This book is written for users who have some knowledge of assembler language programming concepts and some experience in writing assembler programs. AIXwindows programming manuals: SBOF-1528 (User information for AIXwindows is included in the AIX non-programming SBOF) > AIX User Interface Programming Concepts for IBM RISC System/6000, SC23-2209, serves as the programmer's main source book for learning about the user interfaces from a programming perspective. > AIX Graphics Programming Concepts for IBM RISC System/6000, SC23-2208, serves as the programmer's main source book for learning about graphics capabilities from a programming perspective. Note: Not included in the SBOF but recommended for use is AIX Calls and Subroutines Reference (6 vols.) SC23-2198. It is included in the AIX programming manuals SBOF and can also be ordered separately as needed. FORTRAN: SBOF-xxxx > User's Guide for IBM AIX XL FORTRAN Compiler/6000, SC09-1257, explains how to develop and compile FORTRAN language programs on an IBM RISC System/6000 system unit that has the IBM AIX XL FORTRAN Compiler/6000 licensed program installed. > Language Reference for IBM AIX XL FORTRAN Compiler/6000, SC09-1258, describes the syntax and semantics of the FORTRAN programming language that is implemented by the IBM AIX XL FORTRAN Compiler/6000 licensed program. This book is written for users who have some knowledge of FORTRAN language programming concepts and some experience in writing FORTRAN programs. PASCAL: SBOF-xxxx > User's Guide for IBM AIX XL Pascal Compiler/6000, SC09-1326, explains how to develop and compile Pascal language programs on a RISC System/6000 system unit that has the IBM AIX XL Pascal Compiler/6000 licensed program installed. > Language Reference for IBM AIX XL Pascal Compiler/6000, SC09-1327, describes the syntax and semantics of the Pascal programming language that is implemented by the IBM AIX XL Pascal Compiler/6000 licensed program. This book is written for users who have some knowledge of Pascal language programming concepts and some experience in writing Pascal programs. Editors Note: I got this compilation from the ITSC. It is by no means a complete list of documentation for the \risc, but a compilation of the most important system literature. =========================================================================== =========================================================================== You can't let mediocrity win| Hello, this is AIXTIPS NEWS, an additional service from the AIXTIPS group. From now on when ever we feel there is some information that you need immediate, we will send it out as AIXTIPS NEWS. This file will not be cumulative, you have to save it somewhere before you receive a new one. But we will also maintain a AIXTIPS NEWSLOG file for those who join the service later. Get the newslog with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWSLOG If you got this file as a copy and want to have any future versions sent to your reader automatically use the command: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC SUB AIXTIPS NEWS BEWARE| This file has to be treated as IBM CONFIDENTIAL| have fun AIXTIPS at MUNIVM4 #################################################################### 90.12.18 Table of contents: 1. New AIX 3 Infos from NATBOARD 2. A prototyping tool for MOTIF 3. WORM Drives in Germany 4. APL for (S/6000) 5. Exabyte and /6000 6. Telnet problems with OEM machines and update 3002 7. More stuff from Natboard: PS/2 8. Merry Xmas =========================================================================== 1. New Infos from NATBOARD This is for those that don't have natboard access: ******************************************************* RISC SYSTEM/6000 COMPUTE INTENSIVE PERFORMANCE UPDATED TO INCLUDE THE 550 AND NEW COMPETITIVE SYSTEMS November 21, 1990 IBM Internal Use Only An updated version of this presentation guide for the RISC/System 6000 family of POWERstations/POWERservers is now available on the PEC Tools disk. This presentation compares the compute intensive (or technical computing) performance of the RISC System/6000 including the latest POWERstation/POWERserver 550 and representative competition (including DEC, Sun, MIPS) for the following benchmarks. . Dhrystone 1.1 . Linpack (single/double prec.) . Whetstone (single/double prec.) . Livermore Loops (double prec.) . SPEC Suite Release 1.0 To obtain this package, please issue the following command: TOOLS SENDTO DALVM41B TOOLS PEC GET RS6CIP PACKAGE To subscribe to this package in order to receive updates automatically, please issue the following command: TOOLS SENDTO DALVM41B TOOLS PEC SUB RS6CIP PACKAGE ******************************************************* DALLAS SYSTEMS CENTER TECHNICAL BULLETIN "AIX/370 TUNING GUIDE" (GG22-9488) is available. This document is intended to provide systems administrators and users with neccesaary information to assist them in optimizing and tuning the AIX/370 operating system. In addition, some system tools and utilities are mentioned to help users analyze their system performance. The document is not yet orderable from Mechanicsburg, however "softcopies" in the form of a CMS LIST3820 file can be obtained by sending a note to JISHAM @ DALVM41B. The softcopy of the document will be available in this manner until the publication can be ordered using normal procedures. ******************************************************* RISC SYSTEM/6000 QUICK PRICER The RISC System/6000 Quick Pricer can now be ordered from Mechanicsburg. The form number for ordering is: G320-9881 **** NB: this document contains U.S. prices =========================================================================== 2. A prototyping tool for MOTIF EZX--QUICK INTERFACE DEVELOPMENT TOOL FOR MOTIF BEGINS SHIPMENT Sunrise Software International Inc., an IBM business partner, has begun shipping their ezX product on the RISC System/6000 running AIX V3.1. The ezX software is a rapid application development tool used to create a fully operational graphical user interface without programming. The ezX software runs with and created interfaces that operate in the AIXWindows environment (X-Windows/MOTIF). ezX can be used by end users and salespeople, in addition to programmers to design, demonstrate, and evaluate the look and feel of an application before any code is written. It can help simplify the application program by providing a subroutine library that allows the programmer to deal with simple, intuitive graphical functions rather than MOTIF widgets and gadgets. Thus it is not necessary to spend months learning how to program in MOTIF in order to create the graphical interfaces. ezX supports rapid prototyping. The user interface is drawn using the menus, push buttons, lists, data entry fields, graphics images, and much more. This interface can then be demonstrated immediately with full functionality including menu operation, data entry, pulldown menus, etc. This capability allows the end user to review and approve the look and feel of the application before a single line of code is written and thus will greatly reduce the cost and schedule impact of the end-user not operating the product until it is nearly complete. ezX provides portability between various graphical user interfaces. The link between the application program and ezX is the same for multiple GUIs like MOTIF and Open Look. This would allow an application to be ported from a MOTIF look and feel to an Open Look implementation without changes, if it had been created using ezX. Future versions of ezX will also support Presentation Manager, Microsoft Windows, and Macintosh. For further infomation about the ezX product please contact: Fred Sells - Vice President - Marketing Sales: Barry McQuilken Sunrise Software International, Inc. (401) 847-7868 ezX is a trademark of Sunrise Software International RISC System/6000, AIX, AIXWindows, Presentation Manager, are trademarks of International Business Machines Corp. MOTIF is a trademark of the Open Software Foundation X-Windows is a trademark of Massachusetts Institute of Technology Macintosh is a trademark of the Apple Computer Inc. Open Look is a trademark of SUN Microsystems Inc. Windows is a trademark of MicroSoft Corp. **** NB: the product is available to non-US customers =========================================================================== 3. WORM Drives in Germany: 1. WORM und Wiederbeschreibbare optische Platten 5 1/4 Zoll, 600 MB, bereits an der /6000 getestet und verf}gbar Fa. RacTech aus Hennef/Sieg 2. Fa. IBZ aus Frankfurt/Main 70 Platten bis Ende 90/Anfang 91 verf}gbar. =========================================================================== 4. APL for (S/6000) One of the UK VARs has an APL for the RT and RISC System/6000. These are really APL knowlegable folks (I have no interest apart from helping them shift UK RS6K iron ;-) - call: Mr Peter Donnelly or Ms Pauline Brandt Dyadic Systems Riverside View Basing Road Old Basing Basingstoke Hampshire RG24 0AL 0101-44-256-811125 IBM Contact: Brian Mulholland Regards - Ron Beal, UK Systems Management, Basingstoke - BEALRC @ NHBVM7 =========================================================================== 5. Exabyte and /6000 Driver software to support original external exabyte devices on the /6000 is available from the following company in the UK; Willow Ltd, Willow House, 164 Station Road, West Moors, Wimborne, DORSET BH22 OJB Tel 0202-861811 Cheers, Eric W. Appended by: , 86608854 at WARVM2 NB: We use Exabytes as our 8mm systems, but they are unfortunately modified and are not compatible with standard Exabytes. =========================================================================== 6. Telnet problems with OEM machines and update 3002 TELNET PROBLEM IN MULTI-VENDOR TCP/IP ENVIRONMENT WITH AIX VERSION 3. Situation: RISC/6000 has been participating in multi-vendor network without problems. AIX software update "3002" is installed and now some OEM systems cannot successfully telnet to the RISC/6000. All other TCP/IP applications (ftp, rlogin, etc) work fine in both directions. Symptoms: The user executes telnet from the OEM system to the RISC/6000, they receive the "connected to hostname" message, as well as the message defining the escape character, but the user never sees the logon herald. Workaround: Go back to the previous version of /etc/telnetd or use one of the other TCP/IP applications, such as rlogin or rsh., Fix: You may obtain a fix to this problem by contacting the IBM Software Defect Support Center. Reference APAR #IX15621. Recommendation: Before installing update 3002, backup /etc/telnetd to a user's directory. If symptoms are encountered, replace the "3002" telnetd with the saved version. This problem may also be present in the 3003 update of code. From NATBOARD =========================================================================== 7. More stuff from Natboard: PS/2 RECOVERING HARD DISK SPACE FROM AIX PS/2 1.2 INSTALL INTRODUCTION This FLASH is intended to assist SEs and system administrators who have aske d which files they might delete from an AIX PS/2 Base Operating system instal l to recover space. The Base Operating System installation for AIX PS/2 releas e 1.2 incorporates the basic components for a wide range of functionality . Users may not be implementing all of this; an example is the National Languag e support that gets installed with each system. This FLASH details specificall y where files exist on a system that are candidates for removal. The SE or administrator that elects to undertake this process should have a good understanding of the AIX PS/2 operating system. It is assumed the reade r has read IBM AIX PS/2 Managing The Operating System, SC23-2293-00. It is als o assumed that the reader has had past experience in AIX system administration. THE REMOVAL PROCESS The first step to this process is to make sure that you have a good backup o f your working system. If you don't, you will definitely want to make one . This process is described in Managing the Operating System. You always wan t to be able to restore the system back to where you started. The next thing is to understand the system configuration. The list of file s given in this document, while generally not used, may be in certain custome r configurations. One example of where some of these files are used is th e National Language support in an international account. One other situation i s the Berkley commands that are a matter of user preference. The last concern is application of updates. If the system has a Correctiv e Service level applied following the removal process, any files which migh t have been updated in the corrective service will get re-installed. The impac t of applying and committing a Corrective Service is that you may need to remov e some of these files a second time. LIST OF AIX PS/2 V1.2 FILES THAT ARE CANDIDATES TO BE REMOVED: ./generic/adm/mailreturns ./generic/adm/messages ./generic/adm/shutdownlog ./generic/auxcons ./generic/clm ./generic/clmlock@ ./generic/coredumps ./generic/default ./generic/dumpdates ./generic/dumplocks ./generic/environment ./generic/filesystems ./generic/init.state ./generic/inittab ./generic/install/generic.i386 ./generic/install/generic.i386/mhdboot ./generic/install/generic.i386/mhdboot0 ./generic/install/generic.i386/mhdload ./generic/install/local/adm/cron/.proto ./generic/install/local/adm/cron/queuedefs ./generic/install/local/adm/ras/.trcevents ./generic/install/local/adm/ras/eladesc ./generic/install/local/ddi/i386/c327 ./generic/install/local/ddi/i386/descriptions ./generic/install/local/ddi/i386/diskette ./generic/install/local/ddi/i386/ethernet ./generic/install/local/ddi/i386/hft.ddi ./generic/install/local/ddi/i386/hft.kaf ./generic/install/local/ddi/i386/mdkaf ./generic/install/local/ddi/i386/nty ./generic/install/local/ddi/i386/nty.kaf ./generic/install/local/ddi/i386/opprinter ./generic/install/local/ddi/i386/opprinter.kf ./generic/install/local/ddi/i386/options ./generic/install/local/ddi/i386/osprinter ./generic/install/local/ddi/i386/osprinter.kf ./generic/install/local/ddi/i386/plotter ./generic/install/local/ddi/i386/plotter.kaf ./generic/install/local/ddi/i386/pprinter ./generic/install/local/ddi/i386/pprinter.kaf ./generic/install/local/ddi/i386/pty ./generic/install/local/ddi/i386/rty ./generic/install/local/ddi/i386/rty.kaf ./generic/install/local/ddi/i386/sprinter ./generic/install/local/ddi/i386/sprinter.kaf ./generic/install/local/ddi/i386/tape ./generic/install/local/ddi/i386/token ./generic/install/local/ddi/i386/tty ./generic/install/local/ddi/i386/tty.kaf ./generic/install/local/i386/inittab ./generic/install/local/ident ./generic/install/local/local.ldb ./generic/install/local/net ./generic/local.init.dir ./generic/locks ./generic/lpd/qdir ./generic/lpd/stat ./generic/motd ./generic/mtab ./generic/newsite ./generic/newsite.bkend ./generic/pciptys ./generic/ports ./generic/preserve ./generic/ps_data ./generic/root ./generic/spool/logs ./generic/spool/qftp ./generic/statmon ./generic/system.ps2 ./generic/tmp ./generic/undochkpt ./generic/unix.ps2 ./generic/utmp ./usr/lib/nls/ascii.ctab ./usr/lib/nls/ascii ./usr/lib/nls/canadian.ctab ./usr/lib/nls/canadian.en ./usr/lib/nls/canadian ./usr/lib/nls/collating.awk ./usr/lib/nls/danish.ctab ./usr/lib/nls/danish.en ./usr/lib/nls/danish ./usr/lib/nls/dutch.ctab ./usr/lib/nls/dutch.en ./usr/lib/nls/dutch ./usr/lib/nls/environment.aw ./usr/lib/nls/example.ctab ./usr/lib/nls/finnish.ctab ./usr/lib/nls/finnish.en ./usr/lib/nls/finnish ./usr/lib/nls/french.ctab ./usr/lib/nls/french.en ./usr/lib/nls/french ./usr/lib/nls/german.ctab ./usr/lib/nls/german.en ./usr/lib/nls/german ./usr/lib/nls/italian.ctab ./usr/lib/nls/italian.en ./usr/lib/nls/italian ./usr/lib/nls/japanese.ctab ./usr/lib/nls/japanese.en ./usr/lib/nls/japanese ./usr/lib/nls/nlin/aus.ger ./usr/lib/nls/nlin/aus.ger.in ./usr/lib/nls/nlin/belgian ./usr/lib/nls/nlin/belgian.in ./usr/lib/nls/nlin/canadian ./usr/lib/nls/nlin/canadian.in ./usr/lib/nls/nlin/dan.nor ./usr/lib/nls/nlin/dan.nor.in ./usr/lib/nls/nlin/fin.swed ./usr/lib/nls/nlin/fin.swed.in ./usr/lib/nls/nlin/french ./usr/lib/nls/nlin/french.in ./usr/lib/nls/nlin/internat.in ./usr/lib/nls/nlin/international ./usr/lib/nls/nlin/italy ./usr/lib/nls/nlin/italy.in ./usr/lib/nls/nlin/japan.latin ./usr/lib/nls/nlin/japan.latin.in ./usr/lib/nls/nlin/portugal ./usr/lib/nls/nlin/portugal.in ./usr/lib/nls/nlin/spanish ./usr/lib/nls/nlin/spanish.in ./usr/lib/nls/nlin/uk ./usr/lib/nls/nlin/uk.in ./usr/lib/nls/nlin/universal ./usr/lib/nls/nlin/universal.in ./usr/lib/nls/nlout/aus.ger ./usr/lib/nls/nlout/aus.ger.out ./usr/lib/nls/nlout/belgian ./usr/lib/nls/nlout/belgian.out ./usr/lib/nls/nlout/canadian ./usr/lib/nls/nlout/canadian.out ./usr/lib/nls/nlout/dan.nor ./usr/lib/nls/nlout/dan.nor.out ./usr/lib/nls/nlout/fin.swed ./usr/lib/nls/nlout/fin.swed.out ./usr/lib/nls/nlout/french ./usr/lib/nls/nlout/french.out ./usr/lib/nls/nlout/internat.out ./usr/lib/nls/nlout/international ./usr/lib/nls/nlout/italy ./usr/lib/nls/nlout/italy.out ./usr/lib/nls/nlout/japan.latin ./usr/lib/nls/nlout/jp.lat.out ./usr/lib/nls/nlout/portugal ./usr/lib/nls/nlout/portugal.out ./usr/lib/nls/nlout/spanish ./usr/lib/nls/nlout/spanish.out ./usr/lib/nls/nlout/uk ./usr/lib/nls/nlout/uk.out ./usr/lib/nls/nlout/universal ./usr/lib/nls/nlout/universal.out ./usr/lib/nls/norwegian.ctab ./usr/lib/nls/norwegian.en ./usr/lib/nls/norwegian ./usr/lib/nls/portugal.ctab ./usr/lib/nls/portugal.en ./usr/lib/nls/portugal ./usr/lib/nls/spanish.ctab ./usr/lib/nls/spanish.en ./usr/lib/nls/spanish ./usr/lib/nls/swedish.ctab ./usr/lib/nls/swedish.en ./usr/lib/nls/swedish ./usr/lib/nls/uk.ctab ./usr/lib/nls/uk.en ./usr/lib/nls/uk ./usr/lib/terminfo/1/1line ./usr/lib/terminfo/1/1linepty ./usr/lib/terminfo/3/3151scan ./usr/lib/terminfo/3/3270 ./usr/lib/terminfo/3/3270-12 ./usr/lib/terminfo/3/3270-12x40 ./usr/lib/terminfo/3/3270-20 ./usr/lib/terminfo/3/3270-24 ./usr/lib/terminfo/3/3270-27 ./usr/lib/terminfo/3/3270-32 ./usr/lib/terminfo/3/3270-43 ./usr/lib/terminfo/9/925 ./usr/lib/terminfo/a/ansi ./usr/lib/terminfo/a/ansi+arrows ./usr/lib/terminfo/a/ansi+cup ./usr/lib/terminfo/a/ansi+erase ./usr/lib/terminfo/a/ansi+idc ./usr/lib/terminfo/a/ansi+idl ./usr/lib/terminfo/a/ansi+idl1 ./usr/lib/terminfo/a/ansi+inittabs ./usr/lib/terminfo/a/ansi+local ./usr/lib/terminfo/a/ansi+local1 ./usr/lib/terminfo/a/ansi+pp ./usr/lib/terminfo/a/ansi+rca ./usr/lib/terminfo/a/ansi+rep ./usr/lib/terminfo/a/ansi+sgr ./usr/lib/terminfo/a/ansi+sgrbold ./usr/lib/terminfo/a/ansi+sgrdim ./usr/lib/terminfo/a/ansi+sgrso ./usr/lib/terminfo/a/ansi+sgrul ./usr/lib/terminfo/a/ansi+tabs ./usr/lib/terminfo/a/arpanet ./usr/lib/terminfo/b/bussiplexer ./usr/lib/terminfo/c/cb-unix ./usr/lib/terminfo/c/cbunix ./usr/lib/terminfo/cvt.ex ./usr/lib/terminfo/d/datakit ./usr/lib/terminfo/d/dialup ./usr/lib/terminfo/d/dumb ./usr/lib/terminfo/e/ethernet ./usr/lib/terminfo/m/minansi ./usr/lib/terminfo/m/mransi ./usr/lib/terminfo/n/net ./usr/lib/terminfo/n/network ./usr/lib/terminfo/p/patch ./usr/lib/terminfo/p/patchboard ./usr/lib/terminfo/p/plugboard ./usr/lib/terminfo/p/pty ./usr/lib/terminfo/t/tvi925 ./usr/lib/terminfo/u/unknown ./usr/lib/terminfo/w/wy60 ./usr/lib/terminfo/w/wy60-S ./usr/lib/terminfo/w/wy60-w ./usr/lib/terminfo/w/wy6v ./usr/lib/terminfo/w/wy6v-w ./usr/lib/terminfo/w/wyse-60 ./usr/lib/terminfo/w/wyse-60-w ./usr/lib/terminfo/w/wyse-60v ./usr/ucb/Mail ./usr/ucb/apply ./usr/ucb/apropos ./usr/ucb/clear ./usr/ucb/edit ./usr/ucb/egrep ./usr/ucb/ex ./usr/ucb/fmt ./usr/ucb/grep ./usr/ucb/groups ./usr/ucb/head ./usr/ucb/last ./usr/ucb/logger ./usr/ucb/lpq ./usr/ucb/lpr ./usr/ucb/lprm ./usr/ucb/mail ./usr/ucb/mailq ./usr/ucb/man ./usr/ucb/newaliases ./usr/ucb/printenv ./usr/ucb/uptime ./usr/ucb/users ./usr/ucb/vi ./usr/ucb/view ./usr/ucb/w ./usr/ucb/wc ./usr/ucb/what ./usr/ucb/whatis ./usr/ucb/whereis ./usr/ucb/which ./usr/ucb/whoami ./usr/ucb/xa370 OTHER CANDIDATES FOR REMOVAL The AIX PS/2 1.2 version may contain some corrupt files if the system has bee n abnormally terminated or if the commands are abnormally suspended. Thes e commands are easily identifiable by the extension deletemeaaay* appended t o the file name, the "*" here represents a wild card character that is matche d by one or more characters. These files are of no use and do take up space . In order to identify them, you can use the AIX find command. The syntax fo r this command is: #find / -name "*deletemeaaay*" -print The # prompt means you are running this command as root or superuser. Thi s will return a list of all deletemeaaay* type files on the system. The next step is to delete them; however, we need to be careful and delet e only the specific files. The procedure is: #find / -name "*deletemeaaay*" -exec rm -i {} \; This command will return each individual match and interactively ask if yo u would like to remove it. After you are sure you are removing only the file s you want, the -i option for rm can be removed and the following command can b e used: #find / -name "*deletemeaaay*" -exec rm {} \; This command can be added in a routine system maintenance procedure like a shell script, crontab, or the skulker command. For more information o n skulker and system maintenance see AIX PS/2 Commands Reference, Volume 2 an d AIX PS/2 Managing The Operating System. REFERENCES IBM AIX Managing The Operating System, SC23-2293-00 IBM AIX Commands Reference Volume 1, SC23-2292-00 IBM AIX Commands Reference Volume 2, SC23-2184-00 =========================================================================== 8. Merry Xmas The aixtips news service will go on winter vacation. We resume operation on January the seventh. Merry Xmas and a happy new year| Oder An guadn Rutsch| =========================================================================== =========================================================================== The UNIX Philosophy Ken Thompson has an automobile which he helped design. Unlike most automobiles, it has neither speedometer, nor gas guage, nor any of the other numerous idiot lights which plague the modern driver. Rather, if the driver makes a mistake, a GIANT "?" lights up in the center of the dashboard. "The experienced driver," says he, "will usually know what's wrong." Orignal source unknown; found on Joseph Evans' (Electrical and Computer Engineering professor at Kansas University) door. #################################################################### 91.04.05 Table of contents: 91049. Again: Emacs for the /6000 91050. User Interface Language (UIL) for OSF/Motif with AIX V3.1 91051. How do I minimize the space needed for AIX 3 on the box 91052. Some warnings about update 3005 / AIX 3.1.5 and old hardware 91053. Motif 1.1.1 and X11 R4 (Client) available from Sunrise Software 91054. NLS support for as400xfer 91055. Yet another Emacs tip 91056. How do I decrease the pagingspace on AIX 3? 91057. How do I stop X without breaking my fingers 91058. xdm for the /6000 91059. HARDWARE FORUM ========================================================================= The ITSC Austin sponsored a 3-week residency to study the features of UIL. The purpose of this residency was to gain an introductory understanding of how to use the OSF/Motif User Interface Language (UIL) and the Motif Resource Manager (MRM). The output of this residency project is an internal document which is available on the AIXTOOLS disk. Abstract of document: ===================== The User Interface Language (UIL) is a high level language which describes the initial state of a Motif user interface. This paper investigates the purpose of UIL and gives an overview of its functionality. After a short description of what UIL is all about, a complete example is given to demonstrate how to use UIL. Particular aspects of UIL which may not be obvio to first-time users are also described. There is an evaluation of the strengths and weaknesses of UIL implied in the "Summary" section. The International Technical Support Center (ITSC) in Austin sponsored a 3-week residency to study the features of UIL. The purpose of this residency was to gain an introductory understanding of how to use both UIL and the Motif Resource Manager (MRM). The resulting research provided the content for this paper. ======================================================================== To get a copy of this document in LIST3820 tersed format, submit a request in the following form: TOOLS SENDTO YKTVMV TOOLS AIXTOOLS GET UIL PACKAGE You will receive three files. They are: UIL README * this file UIL TRS3820 * printable file UIL TRSSCPT * script source To reduce network traffic we have compressed the files with the VM terse command. You have to uncompress the source file and the printable file, before you are able to use them. The following commands will uncompress the files. TERSE UIL TRSSCPT A UIL SCRIPT A (UNPACK TERSE UIL TRS3820 A UIL LIST3820 A (UNPACK The SCRIPT file can be used to process the file for other printers. The LIST3820 is a ready to print version on 3820, 3825 and 3827 printers. Please send comments to Peter Koepp (KOEPP at AUSVM8), ITSC AUSTIN Regards Peter Koepp ======================================================================== 91049. Again: Emacs for the /6000 This is for those whose customers have internet access: Anonymous ftp to prep.ai.mit.edu, cd to /u/emacs, and get (binary mode) the file emacs-18.58.tar.Z. Uncompress, untar, read the INSTALL document, etc. i tried it and got a working emacs. uwe untermarzoner ======================================================================== 91050. User Interface Language (UIL) for OSF/Motif with AIX V3.1 User Interface Language (UIL) for OSF/Motif with AIX V3.1 ========================================================= The ITSC Austin sponsored a 3-week residency to study the features of UIL. The purpose of this residency was to gain an introductory understanding of how to use the OSF/Motif User Interface Language (UIL) and the Motif Resource Manager (MRM). The output of this residency project is an internal document which is available on the AIXTOOLS disk. Abstract of document: ===================== The User Interface Language (UIL) is a high level language which describes the initial state of a Motif user interface. This paper investigates the purpose of UIL and gives an overview of its functionality. After a short description of what UIL is all about, a complete example is given to demonstrate how to use UIL. Particular aspects of UIL which may not be obvio to first-time users are also described. There is an evaluation of the strengths and weaknesses of UIL implied in the "Summary" section. The International Technical Support Center (ITSC) in Austin sponsored a 3-week residency to study the features of UIL. The purpose of this residency was to gain an introductory understanding of how to use both UIL and the Motif Resource Manager (MRM). The resulting research provided the content for this paper. ======================================================================== To get a copy of this document in LIST3820 tersed format, submit a request in the following form: TOOLS SENDTO YKTVMV TOOLS AIXTOOLS GET UIL PACKAGE You will receive three files. They are: UIL README * this file UIL TRS3820 * printable file UIL TRSSCPT * script source To reduce network traffic we have compressed the files with the VM terse command. You have to uncompress the source file and the printable file, before you are able to use them. The following commands will uncompress the files. TERSE UIL TRSSCPT A UIL SCRIPT A (UNPACK TERSE UIL TRS3820 A UIL LIST3820 A (UNPACK The SCRIPT file can be used to process the file for other printers. The LIST3820 is a ready to print version on 3820, 3825 and 3827 printers. Please send comments to Peter Koepp (KOEPP at AUSVM8), ITSC AUSTIN Regards Peter Koepp ======================================================================== 91051. How do I minimize the space needed for AIX 3 on the box Check out the following package on AIXTOOLS: SCALPEL PACKAGE created by MARKJOHN at AUSVM8. Scalpel - scripts to help remove portions of AIX V3 Get it with TOOLS TO AIXTOOLS GET SCALPEL PACKAGE ======================================================================== 91052. Some warnings about update 3005 / AIX 3.1.5 and old hardware ******************** IBM CONFIDENTIAL ****************************** Subject: Warning Message after ICR1B Installation ===================================================================== The following note(s) is a description of a "Warning Message" which MAY be displayed when a system with a particular system configuration Boots Up with ICR-1B level AIX Operating System. This note was distributed to all the Remote Porting Centers and Technical Support Centers. It is placed here for your general information. The attached note has been sent to all our Remote Porting Centers and Technical Support Centers. It describes a "WARNING Message" which COULD (depending upon system configuration) be displayed during Boot-Up of a RISC System/6000 with ICR-1B level AIX Operating System installed. ICR-1B is AIX 3.1.5 level, also known as update level 3005. In addition to this "Warning Message" description, which is contained in this Base note, I shall append two (2) Responses, as follows: - Response 1 is the CE Instruction Letter concerning the Bluebonnet hardware configuration problem. - Response 2 is the CE Instruction Letter concerning the Token Ring & Skyway hardware configuration problem. ==================== Attachment ======================================== SUBJECT: WARNING message concerning potential hardware configurations The following information relates to a message you may get after applying th ICR1B updates: --------------------------------------------------------------------- WARNING! A POTENTIAL CONFLICT EXISTS IN YOUR SYSTEM HARDWARE CONFIGURATION OPERATING YOUR SYSTEM WITH THIS CONFIGURATION MAY RESULT IN UNDETECTED DAT LOSS. PLEASE CONTACT YOUR IBM SERVICE REPRESENTATIVE WITH SERVICE REQUEST XXX-XXX. Subject: Software detection of high risk BB and TR configs. The new message that some of you are seeing at IPL time is a program proposed by hardware architecture that would detect configurations of Bluebonnet and Token-Ring's that present a risk of data loss due to the known defects with those adapters. The detection will be performed by software during the IPL sequence. The procedure is as follows: 1. Display a warning message on the operator console that a problem exists with the system configuration. 2. Mail a warning message to all system group users that a problem exists. 3. Halt the ipl process for up to 15 seconds to give the user time to read the warning. 4. Make an entry in the error log of this event. Here is the detail logic for the config test. Bluebonnet is straight forwa Token - ring is a bit more complicated. Bluebonnet---------- If the following conditions are detected for any type system send warning. one or more Bluebonnet part no 59F3527, 70F9735, 70F9794, 71F0232, 71F1172, 71F0114 present. AND greater than 2 BB adapters of any vintage present OR any 2 unknown adapters are present. Token-ring ---------- If the following conditions are detected send warning Token-ring part no 74F4134, 53F6052, 53F6046, 39F7824, 53F6064 is present AND any Skyway adapter is present AND the system type is not 7012 (Llano) AND the absolute slot displacement between any TR(listed above) and any Skyway is greater than 2. OR ------------- Token-ring part no 74F4134, 53F6052, 53F6046, 39F7824, 53F6064 is present AND any Skyway adapter is present AND the system type is 7012 (Llano) AND the absolute slot number of TR is LESS than the absloute slot number of Skyway. AND the absolute slot displacement between any TR(listed above) and any Skyway is greater than 2. OR -------------- Token-ring part no 74F4134, 53F6052, 53F6046, 39F7824, 53F6064 is present AND any Skyway adapter is present AND the system type is 7012 (Llano) AND the absolute slot number of TR is GREATER than the absloute slot number of Skyway. AND the absolute slot displacement between any TR(listed above) and any Skyway is greater than 1. ========================================================================s:ear warning */ *** CE Letter describing Bluebonnet Hardware Configuration problem *** CE INFORMATION FOR SERVICE REQUEST NUMBER 869-210 WHEN This SRN may appear in a console warning message and/or appear in the mail box for system group users and be recorded in the system error log. This warning may occur after SCSI microchannel adapters have been added to the system, non-IBM adapters have been added to the system, or AIX version 3.x.x or greater has been installed. PROBLEM The AIX system IPL procedure has determined that the EC level and quantity of SCSI microchannel adapters installed in the system present a risk of undetected data loss under extremely heavy microchannel loading conditions. The SCSI adapters affected are part no. 59F3527, 70F9735, 70F9794, 71F0114, 71F0232, and 71F1172. Heavy loading conditions can occur when a combination of at least three SCSI adapters and other burst mode microchannel devices (IBM and non-IBM) are present and one or more of the SCSI adapters has a part number listed above. CORRECTIVE ACTION Replace all SCSI adapter cards that match the part numbers listed above with new SCSI adapter cards. Access RETAIN for the proper ECA number to order. Interim Corrective Action #1 Reconfigure the customers system utilizing only two SCSI adapters until the old adapters have been replaced. Interim Corrective Action #2 If there are only three SCSI adapters, determine the type of other adapter cards installed in the system. If more than one (adapter type or quantity) of the adapters listed below is installed then follow Interim Corrective Action #1 until all affected SCSI adapters can be replaced. If only one of the adapters listed below is installed then the system is safe to operate as configured until all affected adapters can be replaced. 4 Port Multiprotocol adapter Ethernet adapter Token-ring adapter color or mono graphics adapter 3D graphics adapter S/370 host interface adapter 5086 interface adapter 5085 interface adapter any non-IBM adapter: ====================================================================== *** CE Letter Describing T.R./Skyway Hardware Configuration problem *** CE INFORMATION FOR SERVICE REQUEST NUMBER 850-920 WHEN This SRN may appear in a console warning message and/or appear in the mail box for system group users and be recorded in the system error log. This warning may occur after token-ring and/or color or grayscale graphics microchannel adapters have been added to the system or have had their slot location changed or a new version of AIX has been installed. PROBLEM The AIX system IPL procedure has determined that the slot location of some token-ring adapters relative to the slot location of graphics adapters (greyscale & mono) installed present a risk of undetected data los under rare circumstances. This problem may occur with the following token-ring adapter part nos.: 74F4134, 53F6052, 53F6046, 53F6064, and 39F7824. CORRECTIVE ACTION This corrective action procedure applies only to those token-ring adapters listed above. Other token-ring adapters are not affected. NOTE: All examples below show lowest to highest number card slot. Consult RETAIN for the proper ECA number to order replacement parts. For systems with one graphics adapter..... 1) If one token-ring adapter is present in the system, reconfigure the token-ring (TR) adapter and graphics (GA) adapter as follows: (TR,GA or GA,TR) 2) If two token-ring adapters, reconfigure as follows: (TR,GA,TR or TR,TR,GA) 3) If three token-ring adapters, reconfigure as follows: (TR,TR,GA,TR) 4) If four token-ring adapters, replace one adapter with a new adapter and reconfigure the remaining adapters as shown in 3) above. The new token-ring adapter may be placed in any other available slot. For system with two graphics adapters..... 1) If one token-ring adapter is present in the system, reconfigure the token-ring (TR) adapter and graphics (GA) adapters as follows: (TR,GA,GA) 2) If two token-ring adapters and a) the system type is 7012, replace one adapter with a new adapter and reconfigure as follows: (TR,GA,GA,TR-new) b) the system type is not 7012, reconfigure as follows: (TR,GA,GA,TR) 3) If three token-ring adapters, replace one adapter with a new adapter and reconfigure the remaining adapters as shown in 2b) above. The new token-ring adapter may be placed in any other available slot. 4) If four token-ring adapters, replace two adapters with new adapters and reconfigure the remaining adapters as shown in 2b) above. The new token-ring adapters may be placed in any other available slots. Peter Koepp, ITSC - Austin April 1, 1991 ======================================================================== 91053. Motif 1.1.1 and X11 R4 (Client) available from Sunrise Software If your customer can not wait ages until IBM is ready to deliver Motif 1.1 and X11.4, then this might help: X11 R4 (client) & MOTIF 1.1.1 are commercially available NOW from Sunrise Software P.O. Box 329 Newport, RI 02840 Voice (401) 847-7868 Fax " " 7879 Price: $200 BL NY Wall st belarri@nycvmic4.iinus1.ibm.com Note: This seems to be only the client side. You still will run our X11.3 server. ======================================================================== 91054. NLS support for as400xfer Since the workaround for NLS via imap,omap,setmap (offered in a previous QA entry) was not feasible, I successfully patched e5250 and as400xfer for Austrian/German NLS support. Feel free to contact me offline. For countries other than Austrian/German/US I can provide some infos how I did it..... Werner Stark, AIX Novice BO Linz-Austria (61813675 at VIEVMA) ======================================================================== 91055. Yet another Emacs tip: From the internet: comp.unix.aix: ----------------------------------------------------------------------- The RS/6000 arrow keys don't work correctly under X11. They can be made to work in x11term.c by removing the #ifndef AIX/#endif duo from around the second stringFuncVal() routine, as well as the duo around the if/then/else following case KeyPress in the XPending() loop. ----------------------------------------------------------------------- The RS/6000 backspace key, as well as PageUp/PageDown, don't work under X11. This can be solved in x11term.c like this: case KeyPress: #ifdef AIX XRebindKeysym(XXdisplay, 0xff08, NULL, 0, "\177", 1); /* backspace */ XRebindKeysym(XXdisplay, 0xff55, NULL, 0, "\326", 1); /* page up */ XRebindKeysym(XXdisplay, 0xff56, NULL, 0, "\026", 1); /* page down */ #endif /* AIX */ (This is case KeyPress in the XtPending() loop in x11term.c.) ----------------------------------------------------------------------- Good luck; your mileage may vary... Marc -- Marc Andreessen___________University of Illinois Materials Research Laboratory Internet: andreessen@uimrl7.mrl.uiuc.edu____________Bitnet: andreessen@uiucmrl ======================================================================== 91056. How do I decrease the pagingspace on AIX 3? Tip number: 24.00.07 Title1: Decreasing the Pagingspace Author: Volker Kuhm Date: 91.03.04 Version: 1 >>>>>> How do I decrease the pagingspace on a /6000 A /6000 allways needs to have pagingspace when AIX V3 is running. If you want to make your pagingspace smaller, then you need to have a second paging space active while you modify the first one. The following steps will guide you through that process, assuming you have one paging space and you want to make it smaller. As usual when playing tricks with the system we assume you have a valid backup! -> Create a second pagingspace. mkps -s pp vg pv pp: the size of the pagingspace in physical partiton (usually 4Mb) units vg: the volumegroup where the paging space should be created pv: the physical volume for the pagingspace if the volume group has multiple physical volumes. lsps -a to check what you created -> Activate the pagingspace. swapon /dev/YourNewPagingspace -> Change the characterisitcs of the pagingspaces. chps -a no hd6 To disable the old pagingspace chps -a yes YourNewPagingspace To enable you new pagingspace -> Modify /etc/rc.boot4 . Comment out the swapon /dev/hd6 and add swapon /dev/YourNewPagingspace -> Now update the bootimmage bosboot -a -> Reboot the machine shutdown -Fr -> Check if everything is all right. lsps -a -> Remove the old paging space. rmps hd6 If you want to keep using a pagingspace with the name hd6 then you should repeat the above steps with a slight modification: mklv -y hd6 -t paging vg pp pv vg pp pv: see above chps -a no YourNewPagingspace chps -a yes hd6 edit /etc/rc.boot4 and reverse the changes bosboot -a shutdown -Fr lsps -a rmps YourNewPagingspace ======================================================================== 91057. How do I stop X without breaking my fingers Change your $HOME/.mwmrc file or /usr/lib/X11/system.mwmrc. Modify the Quit menu entry from "Quit" f.quit_mwm to "Quit" f.exec "/usr/lpp/X11/Xamples/clients/xkill/xkill -all" This assumes you have compiled the samples that come with AIXwindows. If you haven't done so yet, do it now: 1. Make sure the date is set correctly. 2. Type "cd /usr/lpp/X11/Xamples" 3. Type "touch Imakefile" 4. Type "make Makefile" 5. Type "make World" This will take a while .... The xkill program will prompt you in the initial window to press the three mouse buttons from right to left. Do it in the root window (on the gray background). See /usr/lpp/X11/Xamples/clients/xkill/xkill.man for documentaion. ======================================================================== 91058. xdm for the /6000 If you would prefer to directly log into X instead of an HFT, then xdm might be of help. Get a complete installp immage with the command TOOLS SENDTO MUNIVM4 AIXDOC AIXTOOLS GET XDM INSTALLP It will modify /etc/inittab to start up xdm instead of the console. It comes complete with source. It can also be used as an example on how to create installp immages. ======================================================================== 91059. HARDWARE FORUM There is a new forum on IBMUNIX to discuss OEM Hardware for the /6000: The purpose of this FORUM is to discuss available, or nearly available 3rd Party Hardware solutions for the Risc System 6000 and AIX environment Please limit discussion to product specs, vendor contact info, and any experiences with the hardware solution. ======================================================================== ======================================================================== God made the integers; all else is the work of Man. -- Kronecker #################################################################### 91.04.23 Table of contents: 91060. Beware of the FORTRAN MCLOCK Subroutine 91061. RISC System/6000 memory price pitfalls 91062. PROBLEM WITH XSTATION AND ETHERNET HEARTBEAT (SQE) 91063. VMEbus attachment via Bit3 91064. 3480-cartridge tape drive and worm drives for the /6000 91065. RPG on RISC6000 91066. Parameters for rdump on /6000 91067. Something on NIS / yellow pages 91068. More news from the Austrian NFT club ========================================================================= 91060. Beware of the FORTRAN MCLOCK Subroutine > Subject: Performance S/6000 : AIX XL-Fortran Function MCLOCK > > Due to a customer's report on the CPU-performance of the S/6000 > - measured by the XL-FORTRAN supplied FUNCTION MCLOCK - > I think it should be stressed that there is a bug in the AIX XL- > FORTRAN language-reference documentation (SC09-1258). > > In appendix B on page 155 it is stated that MCLOCK measures the time > in units of "one sixtieth (1/60) seconds" which should be corrected > to one hundredth (1/100) seconds. > > (The same error of course holds true for the info-explorer information > on the result of a call to MCLOCK.) > > Please notice that this corresponds to a 'performance improvement' > by a factor of 1.67 | Thx, but the problem has been addressed. In fact, Version 1 GA'd with a README file that included a note of this problem ! I guess we can't make people read the README file, but it should have been no surprise. Naturally it's fixed in the V2 manuals. Cheers, Graham Warren ========================================================================= 91061. RISC System/6000 memory price pitfalls There is an interesting pricing anomaly on the RISC System/6000 memory prices. Example: 7012-320 24 Megabytes $ 6,320.00 (Features 4010, 4008) 32 Megabytes $ 6,000.00 (Feature 4033) Do you think your customer would be interested in an additional 8 Meg of memory for $ 320.00 less money? Can you say: Yes! Actually, there is logic behind this apparent aberration. IBM was losing memory sales to third party chip distributors. It seems the memory IC's are mounted on sockets. So, one could buy the base 8 Meg card, remove the IC's and install 16, 32 or 64 Meg modules. The expense lay in the proprietary base cards, not in the memory chips. The net rule of thumb is don't sell two memory cards, if you can get it all on one. In the above example, the 24 Meg configuration takes two memory cards and the 32 Meg configuration takes one. Art Cannon ACANNON at DALVMIC3 ========================================================================= 91062. PROBLEM WITH XSTATION AND ETHERNET HEARTBEAT (SQE) Here is a copy of the flash for your info (so you don't have to look up HONE). ------------------------------------------------------------------------ A problem with Xstations has been found when using the DIX connection to an Ethernet transceiver. The problem affects the following scenarios when used with the outboard transceiver connection with SQE turned OFF in the transceiver: Xstation 120 using X11.4 X-server (bootfile1) Xstation 130 (bootfile2) The Xstation 120 (with ROS level 1.2 or higher) with the X11.3 X-server (bootfile), can function with SQE either turned on or off in the transceiver. The problem can be corrected by turning SQE ON in the transceiver associated with the Xstation. SYMPTOMS: On the LAN statistics screen, an 8803 error code will appear after the TFTP line for Ethernet while the packets are being transmitted. The 8803 will then be replaced by 0000 after the download/TFTP has completed. Soon after, you will receive the message "Could Not Connect to File Server". Note that this problem is only associated with the DIX (outboard transceiver) Ethernet connection to the Xstations, and only when the SQE function of the transceiver is turned off. This will be fixed in a future version of AIX/Xstation Manager software. The following is a more detailed explanation of the heartbeat (SQE) function on Ethernet: SQE (heartbeat) is a function that is done in the transceiver itself. It sends a 10Mhz signal back to the Ethernet adapter whenever the adapter has finished transmitting a block of information. The purpose of this is so that the adapter can check it's collision detection circuitry and the transceive cable connection. The heartbeat (SQE) signal is NEVER put out onto the Ethernet wire. As far as the on-board transceiver, heartbeat is not used because the transceiver is mounted on the circuit board, this is not changeable. (*) Ethernet is a trademark of Xerox Corp. ========================================================================= 91063. VMEbus attachment via Bit3 Nearly exactly one year ago Bit3, one of the major players in the VMEbus arena, announced a card to attach a VMbus crate to RISC System/6000. Now I got nore information about that and , more important, about their SW support. On the HW side there are two cards, the old MCA-VMEbus adapter BIT446 and the new with DMA support BIT477. Transfer rates between VME and MCA go up to 20 MB s^-1. For both adapters they provide device drivers with the same capabilities except for DMA support. The main features are: - physical adapter separated in several "windows" - each window a logical device - logical devices accessed by part of minor number - each logical device allocated to each of the following windows -- adapter registers -- dual port RAM address space -- I/O space on the remote bus -- remote bus mem. in the range 0x00000000 ... 0x7fffffff -- remote bus mem. in the range 0x80000000 ... 0xffffffff Supported call's: read, write, lseek,ioctl Interrupt support memory mapped I/F signal registration for applications (in case of interrupt). The prices in Germany are (converted to $US using 1 $US = 1.5 DM): ( a bit outdated ...) BIT 446 3000 $US BIT 477 6000 $US BIT400-921(SW f. 446) 900 $US BIT400-923(SW f. 477) 1200 $US :-) Heinrich Backhausen RNW AIX Mktg. ========================================================================= 91064. 3480-cartridge tape drive and worm drives for the /6000 ICE INTRODUCES AIX DRIVER TO CONNECT IBM RISC/6000 FAMILY TO IBM 3480-COMPATIBLE CARTRIDGE TAPE DRIVE New product targeted for interchange between mainframes and workstations. HERNDON, VA -- Mar 22, 1991 -- Richard A. Paris, director of technical services of ICE Communications, Inc., announced that the RISC/6000 solutions company has successfully implemented device drivers for the Cipher TapeXpress, the lowest cost 3480-compatible half inch cartridge tape drive on the market today. The new Cipher TapeXpress drive offers 18 tracks of read/write electronics as well as a fully-integrated Small Computer Systems Interface (SCSI). "The Cipher TapeXpress tape drive was chosen as our 3480 solution for the family of RISC/6000 workstations and servers based on performance and price", Mr. Paris commented. "Very simply stated, the Cipher drive uses standard 200 and 220 megabyte 3480-type cartridges. With the addition of the ICE autochanger driver and Cipher autochanger, capacity is increased to 2.2 gigabytes without operator intervention. Benchmarks show performance of 1.5 megabytes per second. That is almost twice the speed of the industry's best-selling reel-to-reel drives and more than six times faster than the 8mm helical scan drives on the market today. This means that the Cipher TapeXpress drive utilizing the ICE driver can transfer 2.2 gigabytes of data in approximately 40 minutes, compared to 2 1/2 hours for 8mm helical scan", he noted. ICE INSTALLS FIRST 5.25 REWRITABLE OPTICAL STORAGE SYSTEM CONNECTED TO IBM RISC/SYSTEM AT NOAA. New product targeted for low cost storage and systems backup needs. HERNDON, VA -- Mar 22, 1991 -- Richard A. Paris, director of technical services of ICE Communications, Inc., announced that the RISC/6000 solutions company has installed a first customer release of Alphatronix's Inspire (R) system at the National Climatic (Data) Center in Ashville, North Carolina. The rewritable optical systems will be used primarily for system backups. The Inspire rewritable optical storage system uses the standard AIX file system providing transparency to operating system commands. Inspire systems feature large storage capacity, random access to stored files, erasability, removability and portability. And because Inspire uses the standard hard disk driver, the need to install and maintain additional drivers is eliminated. Each 5 1/4" rewritable cartridge holds up to 594 megabytes of data. The media conforms to the standards defined by ISO, ANSI, ECMA and Japan Study Committee 23 for cartridge size and format. Inspire supports 512 bytes-per sector media on the RISC/6000. Inspire is ideal for on-line storage because it provides random access to files which is not possible with tape storage. ICE packages the Inspire systems in a variety of configurations with one or two rewritable optical drives, or in combination with a rewritable drive and Winchester drive, Exabyte 8200 or 8500, 1.3 GB DAT or 1/4" streaming tape drive. Inspire jukebox systems providing 16-35 gigabytes of direct access secondary storage are planned for the IBM RISC/6000 family of workstations. For more information, contact: ICE Communications. Inc. 131 Elden Street, Suite 200 Herndon, VA 22070 (703) 478-0309 ========================================================================= 91065. RPG on RISC6000 From: Joe Czajkowski 914-288-3408 (T/L 351-3408) M&S Advanced Workstations & AIX Systems Marketing 44 South Broadway / White Plains, NY 10601 The following is a partial list of companies that are RPG providers for the RISC System/6000. Their offerings typically include a development environment as well as conversion/porting tools and services. Please distribute this list to those in the field who may have opportunity in this area. For additional information, please call the indicated contact directly. ARCCOM Support Group, Inc. (a Jacore value added installer) 1800 Sandy Plains Parkway Suite 320 Marietta, GA 30066 404-424-5345 Contact: Dick Lamborn Comment: Implementation of S/36 RPG II and system support programs under AIX. Emphasis 9855 West 78th St. Suite 240 Eden Prairie, MN 55344 612-941-9337 Contact: Jennifer Reynolds Comment: Migration of S/36 RPG II or ASNA RPG III to RISC6000. The Parkside Organization Inc. 14900 Landmark Blvd. Suite 400 Dallas, TX 75240 214-553-2839 Contact: Jim Lubniewski Comment: Conversion of RPG II source to C source code. Universal Software 4400 MacArthur Blvd. 5th Floor Newport Beach, CA 92660 714-851-8021 Contact: Al Saaverdra Comment: RPG II to RISC6000 migration; S/36 emulation at object code level (July availability). ========================================================================= 91066. Parameters for rdump on /6000 Problem: How do I use the full length of an 8mm taope with rdump? 1. the information about rdump in info-database is uncomplete... 2. therefore the man-page does not tell the whole truth. 3. i will call this in as a bug :-) the solution: after reading the SUN-manpage about rdump it seems that the following invocation of rdump seems to work properly: rdump -s 6000 -d 54000 -0 -u -f host:/dev/rmt0 /u yes, there are the -s and -d flags, which you only will know about if you do a strings /etc/rdump and look at the Usage: ... the values of 6000 and 54000 are directly taken from SUN where they are given for a EXABYTE tape. uwe. stutvm3(untermar) ========================================================================= 91067. Something on NIS / yellow pages I know this might be obvious, but I have had three people do this now, and if they're doing it over here, they're probably doing it all over the world!! The scenario is this. A user decides to configure YP on his/her RISC System/6000. They edit the Makefile in /etc/yp so that the all: stanza now reads: all: passwd group hosts services protocols This will only create NIS maps for passwd, group and hosts on the server. ie that is the only info that the client can request from the server. He or she then runs ypinit to make the NIS maps. The NIS maps are built and before trying to use the NIS services from a client decides to test communications with the network. You can now no longer rsh, rlogin, telnet or even ping out from this server host!!! What has gone wrong? Simple really. They probably had the YP daemons running whilst they were running ypinit! So the solution is to issue stopsrc -g yp before running ypinit and then startsrc -g yp Afterwards when the ypinit process has finished. It has happened twice to me so I hope that this is useful to someone else out there. John Easton 86681182 at WARVM2 ========================================================================= 91068. More news from the Austrian NFT club If you don't know what NFT is all about: It is a nearly fault tolerant setup for the /6000, used in a major bid for the Austrina Railways. Not to be confused with the fault Tolerant NFS server from Yorktown. hallo nftfans, two new PACKAGES are available: request nftdescr from 61806043 at vievma provides a more detailed description about the system. this is based on the updated NFTTISG TEXT file and includes also a lot more information about DASD takeover and setup. request nftcomme from 61806043 at vievma provides a textfile including comments from people who ahve already seen the system in demo or working. both files are also included in the old nftfoils package which can be requested through request nftfoils from 61806043 at vievma the file NFTFOILS SCRIPT from this package now shows an english codepage, so hopefully you will not get in troubles during the scriptrun anymore. ======================================================================== ======================================================================== "VM is a text adventure, if you win, you get to use UNIX" #################################################################### 91.05.06 Table of contents: 91069. What is the RAM size of my /6000? 91070. Tablet on the IBM Xstation 91071. C++ from Comeau Computing 91072. NLS Support patches for the AS/400 Connection program 91073. New malloc options beginning with update 2004. 91074. Debugging the AIX kernel / reading dumps 91075. Performance measurements on GA code (RISC SYSTEM/6000) 91076. Installing AIX PS/2 1.2.1 with the internal tape ========================================================================= 91069. What is the RAM size of my /6000? Run it as root: bootinfo -r ========================================================================= 91070. Tablet on the IBM Xstation From the ITSC: The tablet is supported on both the Xstation 120 and 130, not just the 130. Also the tablet can be connected to the 3rd or 4th serial ports on the 130 when the 130 has the optional PS/2 Dual Async Adapter Feature. The error was that the tablet option for the Xstation was described as using the RISC System/6000 cables for attachment. The tablet attaches to the Xstations using the PS/2 attachment cabling, not RISC /6000 cabling. The RFA said the tablet needed 5083 feature #4015. This is the feature number for RISC/6000 attachment cable. This is not correct for the Xstation 130. The correct Xstation attachment options for the 5083 Model 021 and Model 022 are: 1. Cable kit for tablet attachment to 25 pin PS/2 FC#4030 PN 6247460 This is the normal attachment cable to connect the tablet to the base serial port for either the Xstation 120 or the 130. 2. Cable kit for tablet attachment to 9 pin PS/2 FC#4035 PN 6247461 This cable is used when the tablet is attached to the optional PS/2 Dual Async Adapter on the 130. This Dual Async adapter is a 130 option only. The Dual Async Adapter is not available on the 120. 3. One of the following power supplies depending upon the geography: -US- 120V/60 Hz power supply for PC, PS/2,.. FC#4050 PN 6248469 -EMEA- 220/240v 50 HZ power supply for PC,PS/2 FC#0805 PN 6248483 -Japan- 100v 50/60 Hz power supply for PC,PS/2 FC#2730 PN 6248470 There is one additional point to clarify on the Hone Tablet configuration. Currently no pointing device is identified as an option or assigned automatically. Currently you will get a tablet without a cursor or stylus. This should be corrected to include FC#1511 which is the "4-Button Cursor" and FC#6351 which is the "Stylus". This should be an optional choice of one or the other of these two features. So for the US when a tablet is ordered for an Xstation the one tablet feature code: FC#4050 for power should be automatically selected as part of the configuration. Then one of the two serial port cable attachment features should be selected either FC#4030 for the 25pin or FC#4035 for the 9 pin. And a pointing device should be selected either FC#1511 for the cursor or FC#6351 for the stylus. Also the Feature Code #3888 Cable kit for 5086 which is now generated as part of the Xstation tablet cables should not be part of the Xstation tablet cables. ========================================================================= 91071. C++ from Comeau Computing Subject: Comeau Computing C++ 2.1!!! RISC SYSTEM/6000 Available! "The last time I saw something run fast was on an Amdahl mainframe!" This quote and others like it were delivered by Greg Comeau. Greg Comeau, of Comeau Computing came into my office, and ported C++ to the Risc System/6000. He was quite impressed with the speed and the ease of which he was able to port to the S/6000. His code is the only 2.1 spec compatible code in the industry today. /* I do not think that is true. afx */ His product is also available on several platforms, but it looks like the S/6000 may be the best. Call Comeau Computing for more info.... Voice (718) 945-0009 ========================================================================= 91072. NLS Support patches for the AS/400 Connection program This is from Austria. They use German there. For other languages you have to use the appropriate code points. Patching e5250 (part of AIX AS/400 Connection Program/6000 5621-051) for NLS ------------------------------------------------------------------------ 1. Verify your NLS problems by following tasks: 1.1 On the RS/6000: start e5250, logon to the AS/400 as USERA send a message containing your NLS characters to USERB on the AS/400 by: SNDMSG + PF4 1.2 On the AS/400: logon as USERB on a native AS/400 terminal look at the message sent from USERA by: DSPMSG 1.3 Repeat this steps using the other direction (from AS/400 to RS/6000) 1.4 You can use the same procedure to verify your patches. 2. Preparing the patch You can try to understand your NLS problems by studying various Codepage tables in AS/400, /370 and AIX manuals...... We preferred the proven "trial and error" method by doing the following steps: 2.1 On the RS/6000: Create a file containing your NLS characters example: vi nls.ascii Print this file in ASCII-Characters and HEX representation example: od -xc nls.ascii > lp0 You will need this Information for patching the e5250 ASCII to EBCDIC translation table. 2.2 On the AS/400: Create and print a similar NLS EBCDIC file You will need this Information for patching the e5250 EBCDIC to ASCII translation table. 3. Applying the patch e5250 contains 4 translation tables. Two of them seem to be used for TCP/IP, which we have not patched up to now. The 2 tables for SNA are: e5250-SNA ASCII to EBCDIC Translation Table starting at Hex'17818' Dec(96280) with Hex'00 01 02 03 37 2D.....' ending at Hex'17917' Dec(96535) with Hex'.....B3 DA FA EA 00 00' e5250-SNA EBCDIC to ASCII Translation Table starting at Hex'17B38' Dec(97080) with Hex'20 A8 A8 A8 A8 A8.....' ending at Hex'17C37' Dec(97335) with Hex'.....FC EA 9A EB E9 A8' Now take your printed NLS "tables": The Hex representaion of a particular character is taken as offset to the beginning of a translation table. You have to change the Hex value on this position to the correct value as in your "NLS table". Start patching the ASCII to EBCDIC Translation Table. Use the already changed values as offsets for patching the EBCDIC to ASCII Translation Table. You can of course calculate the offsets with decimal values. Actually we used the IUO PC-Tool CABLE (PCTOOLS) for the patch and DOSREAD the patched e5250 into AIX. Patching as400xfer for NLS ------------------------------------------------------------------------ 1. Verify your NLS problems by doing actual filetransfers containing your NLS characters. 2. Check with your "NLS Tables" created during e5250 patching. 3. Applying the patch as400xfer contains 4 translation tables. Two of them seem to be rather useless..... The 2 tables for SNA are: as400xfer-SNA ASCII to EBCDIC Translation Table starting at Hex'AADB' Dec(43739) with Hex'00 01 02 03 ....' ending at Hex'ABDA' Dec(43994) with Hex'.... FC FD FE FF' as400xfer-SNA EBCDIC to ASCII Translation Table starting at Hex'ABDB' Dec(43995) with Hex'00 01 02 03 ....' ending at Hex'ACDA' Dec(44250) with Hex'.... FC FD FE FF' Apply the patch as you have done with e5250 Other hints ------------------------------------------------------------------------ If you are browsing e5250, you will find the EBCDIC string KDART...52920002...CQPACTL00....USB..HEX'00650025'... starting at Hex 171B9 (Dec 94649) This string is sent to the AS/400 identifying the 5250 emulation as 5292 Terminal using an US Keyboard and CHRID 104,037 Unfortunately it does not help to merely change this values for example to: AGB...265,273 for Austria/Germany......... The remaining Translation Tables are: e5250 starting at Hex'17613' Dec(95763) with Hex'00 01 02 03 ....' ending at Hex'17712' Dec(96018) with Hex'.....FC FD FE FF' starting at Hex'17713' Dec(96019) with Hex'00 01 02 03 ....' ending at Hex'17812' Dec(96274) with Hex'.....FC FD FE FF' as400xfer starting at Hex'A4E0' Dec(42208) with Hex'00 01 02 03 ....' ending at Hex'A5DF' Dec(42463) with Hex'.....FC FD FE FF' starting at Hex'A5E0' Dec(42208) with Hex'00 01 02 03 ....' ending at Hex'A6DF' Dec(42463) with Hex'.....FC FD FE FF' Actual patch for Austria/Germany ------------------------------------------------------------------------ e5250-SNA ASCII to EBCDIC Translation Table Austrian/German Offset Change (Hex) Character Hex from to ------------------------------------------------- Rufzeichen 21 5A 4F Umlaut u 81 DC D0 Umlaut a 84 43 C0 Umlaut A 8E 63 4A Umlaut o 94 CC 6A Umlaut O 99 EC E0 Umlaut U 9A FC 5A Scharfes s E1 59 A1 Paragraph F5 B5 7C e5250-SNA EBCDIC to ASCII Translation Table Austrian/German Offset Change (Hex) Character Hex from to -------------------------------------------------- Umlaut A 4A BD 8E Rufzeichen 4F 7C 21 Umlaut U 5A 21 9A Umlaut o 6A DD 94 Paragraph 7C 40 F5 Scharfes s A1 7E E1 Umlaut a C0 7B 84 Umlaut u D0 7D 81 Umlaut O E0 5C 99 as400xfer-SNA ASCII to EBCDIC Translation Table Austrian/German Offset Change (Hex) Character Hex from to ------------------------------------------------- Rufzeichen 21 5A 4F Umlaut u 81 81 D0 Umlaut a 84 84 C0 Umlaut A 8E 8E 4A Umlaut : 94 94 6A Umlaut O 99 99 E0 Umlaut U 9A 9A 5A Scharfes s E1 E1 A1 Paragraph F5 F5 7C as400xfer-SNA EBCDIC to ASCII Translation Table Austrian/German Offset Change (Hex) Character Hex from to -------------------------------------------------- Umlaut A 4A 4A 8E Rufzeichen 4F 2B 21 Umlaut U 5A 21 9A Umlaut O 6A 6A 94 Paragraph 7C 40 F5 Scharfes s A1 7E E1 Umlaut a C0 7B 84 Umlaut u D0 7D 81 Umlaut o E0 5C 99 Good luck Stephan Jungwirth, OS/400 (61802787 at VIEVMA) Werner Stark , AIX (61813675 at VIEVMA) ========================================================================= 91073. New malloc options beginning with update 2004. Malloc allways will get memory sizes rounded to the nearest power of two. If you malloc just a little more than one meg, malloc will reserve two meg for you. To get rid of this feature use the call mallopt(1,0); before any malloc call in your program. I suggest using it as the first statement, you never know what the libray functions do. The info-03 CD has some info on mallopt, although it first claimes that mallopt is ignored. Unfortunately none of the READMEs for 3.1.5 or 2004 or 3005 to tell you about this new feature. (I love it!) This version of malloc is also known as the "Yorktown" malloc. Thanks to Mickey for the pointer. ========================================================================= 91074. Debugging the AIX kernel / reading dumps from NATBOARD: Version 1.1 (901218) This document is being developed in stages and will eventually include information concerning the debugging of problems in all major areas of AIX Version 3. The present version describes how to use ' crash ' to debug a system dump. The document includes a description section and appendices containing examples. It also includes a description of the AIX Version 3 address space which is very important for reading system dumps. To receive the document, from your VM account issue the command: TOOLS SENDTO DALVM41B TOOLS AIXIC GET AIXDEBUG PACKAGE To subscribe to the package and receive automatic updates, from your VM account issue the command: TOOLS SENDTO DALVM41B TOOLS AIXIC SUBSCRIBE AIXDEBUG PACKAGE ========================================================================= 91075. Performance measurements on GA code (RISC SYSTEM/6000) This document provides the results of some performance measurements made on the IBM RISC System/6000 with GA code. The tests were run in a controlled environment and may not reflect the actual performance achieved in other environments. Newer versions of the code have made some performance enhancements, but the results in this document will still serve as a guide to the performance of the system. Among other things, this document contains information on some of the standard benchmarks, X-Station performance, disk performance, x11perf and NFS over ethernet and token ring. Additional measurements are being made and will be published as soon as the results are available. To receive this LIST3820 document, enter the following command from your VM account: TOOLS SENDTO DALVM41B TOOLS AIXIC GET GAPERFM PACKAGE ========================================================================= 91076. Installing AIX PS/2 1.2.1 with the internal tape AIX-PS/2 v1.2.1 MEMOTOUSER CORRECTIONS - ITBU INSTALL Installing Base Operating System and LPPs From the Internal Tape Backup Unit Section B.2 of the AIX-PS/2 MemoToUser contains the following statement, regarding installing the Base Operating System and LPPs from the Internal Tape Backup Unit (ITBU). * When installing the Base Operating System from ITBU during initial installation, do not select the "Install from Tape" option. ACTION REQUIRED: Exit from the menu and install using installt It should be disregarded, use the following installation procedure with the ITBU. * To install the Base Operating System from ITBU during the initial installation, proceed as directed in Chapter 3 of Installation and Customizing the Operating System manual. When the "CONTINUE INSTALLATION" menu is reached; place the tape in the drive and select "ITBU Tape" option. After the base installation is complete, the "CONSOLE LOGIN MODE:" menu will be displayed, select the appropriate choice. The "INSTALL PROGRAM PRODUCTS" menu is next, select "Continue Installation". The "POST INSTALLATION" screen will be displayed, press enter. At the "SYSTEM INSTALLATION" menu, select the "End Installation" option (Do not install any LPPs at this time). When the "system halted ..." message is received, press enter and the machine will reboot. Before installing any LPPs, apply the PTF from the diskettes. LPPs may now be installed from tape or diskette as desired. * To install LPPs from the ITBU, install the Base Operating System and boot the machine. If the non-SCSI system BOS has been installed the ITBU must be configured using the devices command. The non-SCSI system is installed if the boot diskettes used have P/Ns 71F0601 and 71F0584. Place the tape in the drive, and use the installt program. It will check the tape for LPPs and then present the "SELECTION MENU". Select the LPPs to be installed by typing in their numbers with spaces in between. Any non-installed LPPs may be installed at a later time if desired. Change the Fstore values to the appropriate one for their system. If the selections are correct, answer yes and the install will begin. When done the "SELECTION MENU" will reappear, the LPPs installed will be marked with an "*". Enter quit to exit the installt program. If the kernel was rebuilt during the install process, reboot the system before continuing. ======================================================================== #################################################################### 91.05.15 Table of contents: 91077. Print screen 91078. Non-Numeric CPU-IDs 91079. NLS support for aixterms displaying on the RT / ps2 from the /6000 91080. Xstation interfacing to serial ports documentation 91081. AIXDEBUG - RISC System/6000 software problem debugging guide revised 91082. How can I recover from a crash when mirroring with only two disks. ========================================================================= 91077. Print screen If you want to capture ascii information, use the command /bin/capture. It will emulate a vt100 terminal and when you press CTRL-P the current screen is dumped to a file. ========================================================================= 91078. Non-Numeric CPU-IDs Each RISC System/6000 processor has a unique internal identifier commonly referred to as the CPU-ID. This CPU-ID is accessible by application programs through the "uname" system call. The X/Open Portability Guide Issue III, which is the relevant standard, states the CPU-ID is a string of unspecified length (AIX defines the length to be 32 bytes) but makes no statement about its content. Software vendors and end users sometimes use the unique CPU-ID to implement software password procedures to discourage unauthorized software copying and execution. Some programmers have erroneously assumed the CPU-ID string to be composed of the ASCII character representation of decimal digits (e.g., 0-9) when they designed their protection procedures. These protection procedures generally fail when the CPU-ID string contains unexpected characters such as hexadecimal digits (e.g., 0-F) or other characters which can happen with the RS6K. Correcting the problems created by this erroneous assumption invariably requires source-code changes by the programmer. The problem may arise when installing new systems, upgrading existing systems, or moving software among systems. Please inform your SPOC, FSC, Porting Center, and Channel Management organizations of this potential problem which may affect business partners and customers. ========================================================================= 91079. NLS support for aixterms displaying on the RT / ps2 from the /6000 The way the RT and the PS/2 handle NLS support under X is different from the way the /6000 does it. On the /6000 the X server handles the NLS stuff, while on the PS/2 and the Rt the aixterms handle NLS. When you want to use a PS/2 or RT as a display for a /6000 aixterm, the following steps should cure the NLS blues: (PS/2 and RT are the same here) ps/2 setup as a german machine copy the /usr/lpp/X11/defaults/xmodmap/$LANG/keyboard file from the /6000 to the ps/2. start X on the ps/2 in a window on the ps/2 run xmodmap on the ps2 with the keyboard file from the /6000. (ignore the warning about Mod2) now start the aixterm on the /6000 with $DISPLAY pointing to the ps/2 you should have full NLS support in the aixterm. ========================================================================= 91080. Xstation interfacing to serial ports documentation May 8, 1991 Early documentation has been made available for those wish- ing to interface non-supported, serial devices to the Xsta- tion with AIX/Xstation Manager Version 1.2 This document provides example code to demonstrate what is needed for customers to be able to write their own programs to interface to serial devices attached to the Xstation. To obtain the documentation, issue the following command from your PROFS command line, or from CMS: TOOLS SENDTO DALVM41B TOOLS AIXIC GET X_SERIAL PACKAGE Contact: DALVM41B(DFERNDEL) ========================================================================= 91081. AIXDEBUG - RISC System/6000 software problem debugging guide revised May 14, 1991 Debugging AIX Problems - AIXDEBUG This document is being developed in stages to eventually include information on the debugging of problems in all major areas of AIX Version 3. This document was titled "Debugging the AIX Kernel". It is now called: AIX Version 3 Software Problem Debugging and Reporting For the RISC System/6000 Version 1.0 As the name indicates, the document now covers a wider range of subjects than just Kernel debugging. The major areas of coverage are: o problem reporting o the system address space and crash o tracing o the error log o boot problems o communications data gathering and problem reporting This section covers both communications device drivers and major areas such as TCP/IP and SNA, and others. o graphics problem determination o performance tools o appendixes on crash problems, communications device driver debugging, and Enternet and token ring sense data. To retrieve this LIST3820 document, enter the following command from your VM account: TOOLS SENDTO DALVM41B TOOLS AIXIC GET AIXDEBUG PACKAGE To subscribe to this package and receive automatic updates, enter the following command from your VM account: TOOLS SENDTO DALVM41B TOOLS AIXIC SUBSCRIBE AIXDEBUG PACKAGE Questions concerning receipt of this document may be directed to DALVM41B (HEISE). ========================================================================= 91082. How can I recover from a crash when mirroring with only two disks. SYSTEM AVAILABILITY WITH 2 DISKS ================================ POURPOSE ======== The pourpose is to increase system availability in a two-disks machine in case of disk failure. BACKGROUND ========== AIX V3 Mirroring requires the disks holding the mirrored data being in the same volume group. The "rootvg" volume group is created at installation time and holds the system data (paging space, boot logical volume, logging file system, /usr, /, /tmp, and /u). Assuming the system has been installed to disk "hdisk0" the second disk "hdisk1" must be added to the "rootvg" volume group if mirroring should be used. In this case "hdisk0" will contain two VGDA's and "hdisk1" will contain one. Now if "hdisk1" fails the system remains available because the majority of VGDA's (the two from "hdisk0") within "rootvg" are active ("quorum" is reached). If "hdisk1" is online and "hdisk0" fails the "quorum" cannot be reached (only one VGDA active) and the system availibility will get lost. In this case any try to boot from "hdisk1" will fail. Using the maintanance diskette in the form explained below will write a second VGDA to "hdisk1" and allow a normal boot from this disk. -------------------------------------------------------------- | | | Please DON'T misunderstand it, following procedure allow | | you booting and using the system after a "hdisk0"-crash. | | There is no guarantee for data consistence. | | | -------------------------------------------------------------- INSTRUCTIONS ============ 1. Add "hdisk1" to the "rootvg" volume group using: extendvg rootvg hdisk1 or the SMIT option: "Add a Physical Volume to a Volume Group" fastpath: smit extendvg 2. Change the characteristics of the logical volumes (LV's) in "hdisk0" to enable mirroring to "hdisk1", and add a boot logical volume to "hdisk1". The LV's to be mirrored are: paging space hd6 filesystem log hd8 /usr hd2 / hd4 /u hd1 /tmp hd3 Use the command: mklvcopy hdX 2 hdisk1 (NOTE: replace X with the values above) or the SMIT option: "Add Copies to a Logical Volume" fastpath: smit mklvcopy 3. Create a boot logical volume (blv) on "hdisk1". Use the commands: mklv -y hd5X -t boot -a e rootvg 2 hdisk1 (NOTE: choice a value for X) bosboot -a -l /dev/hd5X -d /dev/hdisk1 4. Edit the /etc/filesystems file and add following stanza to the end of the file: /blv: dev = /dev/hd5X vol = "spare" mount = false check = false free = false vfs = jfs log = /dev/hd8 5. Update NVRAM with a new list of disks to attempt IPL from: bootlist -m normal hdisk0 hdisk1 6. Create a new "inst/maint" diskette. Use the command: /usr/lpp/bosinst/diskette/mkinstdskt HOW TO BRING UP THE SYSTEM IF "HDISK0" FAILS ============================================ 1. Turn off the machine and turn the key to SERVICE mode. 2. Boot from diskettes using the "inst/maint" diskette you created above. 3. Go into maintanance mode (option 5) 4. Use the command: importvg -y rootvg hdisk0 (NOTE: Use hdisk0 although you want to boot from "hdisk1") You will get the message: "hdisk0 000000XXXXXXXXXX PVMISSING 000000YYYYYYYYYY NONAME . . . importvg: Unable to import volume group from hdisk0" Try a second time. Now you will see: "hdisk0 000000XXXXXXXXXX PVACTIVE 000000YYYYYYYYYY NONAME . . . importvg: Partially succesful importing of hdisk0 rootvg" 5. Enter: /etc/continue hdisk0 (NOTE: always hdisk0) 6. The command: lspv hdisk1 will show that "hdisk1" has got 2 VGDA's. 7. Shutdown and turn off the machine, turn the key to the NORMAL position and boot from "hdisk1". Miguel Crisanto, AIX FSC Munich ======================================================================== ======================================================================== Quality is just a slogan! My impression when watching the IBM MDQ campaign, afx #################################################################### 91.05.31 Table of contents: 91083. AIXpert Publication: Spring 1991 Edition 91084. Performance of Ingres Database on RISC/6000 91085. SCSI DEVICE RESTRICTIONS REMOVED 91086. MVS VIADUCT WILL NOT SUPPORT CICS 3.2 91087. AIX ACCESS FOR DOS USERS V2.1 PCI ERROR (MISMATCHED PCI VERSION) 91088. Academic Information Systems on Higher Education 91089. NOTICE TO OWNERS OF PRE-GA SYSTEMS 91090. White papers from the OSF now in softcopy script format 91091. A comparison of User Interface builders in UniNews 91092. Vital info on the /6000 and how to get it 91093. More disk arrays 91094. How to recover from a 552 error. ========================================================================= 91083. AIXpert Publication: Spring 1991 Edition Now Available from Mechanicsburg May 14, 1991 The Spring edition of the AIXpert, a quarterly publication for AIX software developers is now available. This issue focuses on RISC System/6000 porting, and includes two articles by Gary Andrews which provide a wealth of useful tips and techniques on the porting process. The Software Vendor Technical Support Center in Dallas has contributed a list of twenty frequently asked technical questions and answers. And this issue's executive interview is with Donna Van Fleet. Software vendors may subscribe to this publication by calling the Software Vendor Information Line at 1-800-627-8363, or by completing the insert card in the Winter or Spring issue. IBM employees may order this issue from Mechanicsburg using order number G580-0006-00. Or you may subscribe to this publication using SLSS (System Library Subscription Service) and specifying form number GBOF-1199 (SLSS may be accessed from HONE. If you do not have access to HONE, you can obtain an SLSS form from a branch office.) If you have questions or comments you may contact the editor, Gloria Hardman - RHQVM21/HARDMAN. ========================================================================= 91084. Performance of Ingres Database on RISC/6000 This Flash was prepared by the Austin Performance Group. Any questions about it should be submitted through QUAT. ITSC Austin 17th May 1991 ----------------------------------------------------------- The following information is a result of investigating a customer benchmark with Ingres in Austin. The Ingres release 6.3 FCS that shipped in December of 1990 was not compiled with optimization. A later update 6.3.02p (ris.US5/02) 910409B contains major performance improvements. My understanding is that this level of release is not distributed automatically, but must be specifically requested. This level has 90% of the code compiled optimized. Additionally, there are two Ingress environment parameters that have a poor default value (10,000). These are II_SEM_LOOP and II_GETSPIN_LOOP. These can be modified by using ingsetenv II_SEM_LOOP 5 ingsetenv II_GETSPIN_LOOP 5 The combination of the new code update and the parameter setting netted a substantial performance improvement for the benchmark that was being investigated in Austin. IBM Internal Use Only ========================================================================= 91085. SCSI DEVICE RESTRICTIONS REMOVED Previous to this announcement, the SCSI High Performance Controllers for the IBM RISC SYSTEM/6000 could support up to seven devices only if those devices were either all internal or all external to the system unit. However, when both internal and external devices were attached to the same SCSI controller, there was a previously announced restriction which limited the external devices to two or less. Some users, especially users of the Models 320 and 320H, have expressed a need to attach more than two external devices to a controller that also has internal devices attached. With this announcement, it is now possible to attach more than two external SCSI devices to a SCSI controller with internal devices also attached (up to a combined total of seven devices). An "As Required" EC is available for this specific situation. This EC is appropriate for currently (May 1991) installed RISC SYSTEM/6000 models when the following conditions exist: A). For IBM 7012 Model 320- 1. FC #2828, and 2. The need to exceed two external SCSI devices on that SCSI bus. B). For IBM 7012 Model 32H- 1. The need to exceed two external SCSI devices on the SCSI bus of the base SCSI controller. C). For IBM 7013 Models 520, 530, 540, 550, and 55S- 1. The need to exceed two external SCSI devices on the SCSI bus of the base SCSI controller. OR 1. FC #2829, and 2. The need to exceed two external SCSI devices on that SCSI bus. D). For IBM 7016 Model 730- 1. The need to exceed two external SCSI devices on the SCSI bus of the base SCSI controller. The EC is not required for FC# 2835, SCSI High Performance External I/O Controller. Similarly, this EC is not required for FC # 2828, FC # 2829, or the base SCSI controller when there are two or less external SCSI devices on those busses. The EC provides a pair of modified SCSI Terminators which will condition the SCSI bus to enable attachment of up to a total of seven SCSI devices (both internal and external). The "As Required" EC consists of a model-specific kit which contains an internal SCSI ribbon cable with a new terminator crimped onto the end, plus a new external 50-pin terminator for the last device on the SCSI bus. All new RISC SYSTEM/6000 models having SCSI controllers and having scheduled ship dates on or after June 14, 1991 will have the new cable and terminators. The new internal terminators crimped on the internal SCSI ribbon cable are grey, whereas the previous terminators were black. The new external last-device terminators may be various colors, but will be labeled "P/N 00G0968" (previous terminators were P/N 70F9761). If your customer has an installed RISC SYSTEM/6000 which meets the above criteria, and wishes to add more external SCSI devices in one of the situations previously described, you may obtain an As Required EC at no charge. Ask CE to search RETAIN under the appropriate machine type for "FPT TERM" to obtain the correct field bill for the As Required EC. The As Required EC is expected to be available by late June, 1991. ========================================================================= 91086. MVS VIADUCT WILL NOT SUPPORT CICS 3.2 TITLE: IWSY FLASH 1064 MVS VIADUCT WILL NOT SUPPORT CICS 3.2 MVS VIADUCT WILL NOT SUPPORT CICS 3.2 CICS 3.2 provides connection security internally, allowing only one sign-on per connection. This feature provides tighter security for remote connections. The AIX Viaduct for MVS (5688-189) provides its own connection security and allows multiple sign-ons per connection. Due to the security changes of CICS 3.2, the AIX Viaduct for MVS is not compatible with CICS 3.2. (LH) ========================================================================= 91087. AIX ACCESS FOR DOS USERS V2.1 PCI ERROR (MISMATCHED PCI VERSION) TITLE: IWSY FLASH 1039 AIX ACCESS FOR DOS USERS V2.1 PCI ERROR (MISMATCHED PCI VERSION) **********THIS ENTRY IS FOR IBM INTERNAL USE ONLY********** AIX ACCESS FOR DOS USERS V2.1 PCI ERROR (MISMATCHED PCI VERSION) AIX ACCESS FOR DOS USERS (AADU) This item contains helpful information intended to act as a guide. Normal precautions should be taken in adopting these same techniques and procedures because as product and system interfaces change, so would the usage of this information change. SCENARIO/EXPLANATION: IBM AADU is a LAN software product that connects DOS PCs by using AIX systems as network servers allowing DOS users to share applications, data and printers, even in multivendor networks. Users access shared resources in the environment they understand best, DOS. They see a common shared DOS file system - unaware of the presence of a network or an AIX-based server. Unlike conventional Local Area Network servers, AADU enables AIX hosts to accommodat e a virtually unlimited number of personal computers. The newest version of AADU, version 2.1 currently has a problem communicating with the RISC System/6000. When run, you get the error message: mismatched PCI version. Please note the README FIRST file pages 11 and 12 to fix this problem. If you are missing these pages, contact Defect Support. (CGM) ========================================================================= 91088. Academic Information Systems on Higher Education User Friendly Computing Center Marketing Guide V1.2 May 1, 1991 +--------------------------------------------------------+ | AN ACIS RESEARCH AND AIX SOLUTIONS MARKETING GUIDE | | "THE USER FRIENDLY COMPUTING CENTER" | | | | VERSION 1.2 is now available!! | | | +--------------------------------------------------------+ How does the Client/Server concept relate to computational research ?? What can you do at your university to increase RESEARCH COMPUTING ?? _________________________________________________________________ H O W T O G E T A C O P Y !!! This marketing guide is available on MKTTOOLS. It is pre-formatted and ready to print on your branch office 3820 printer. You can request the package ACISUFCC using the following command: TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET ACISUFCC PACKAGE __________________________________________________________________ P R I N T I N G T H E D O C U M E N T!!! The ACISUFCC LIST3820 file contains the document, already formatted for printing on an IBM advanced function printer (3820 or 3812). It should be duplex printed (two sided). If you are using PUBS (ProcessMaster) to print the file: First select 'U' (general utility functions) from the initial menu, then select 'P' (print formatted file). Fill in the appropriate information on the menus that follow. _________________________________________________________________ This guide is for Marketing Reps, Systems Engineers and managers who have research universities in their territories. It is intended to be a primer on research computing and addresses both large systems and workstations. _________________________________________________________________ If you have questions, contact Ken King (KINGKEN at ATLVM1). ------------------------------------------------------------------------- Ken Hillside 10R01 4111 Northside Parkway Atlanta, GA 30327 ========================================================================= 91089. NOTICE TO OWNERS OF PRE-GA SYSTEMS The Austin project to upgrade FOR FREE pre-GA Risc System/6000s (serial numbers from 2601000 to 2605000) to GA level will be ending 06/30/91. If you have or know of anyone who has a system in this range that has not been upgraded, please contact us immediately to schedule the upgrade. THERE WILL BE NO EXTENSION OF THIS OFFER. Contact: Kathy Mackay tie 678-4242 or (512) 823-4242 ========================================================================= 91090. White papers from the OSF now in softcopy script format The following OSF White Papers are now available in these packages on the AIXMKTG disk (ICTOOLS at SYDVM1). See ordering commands below :- OSF1 PACKAGE 1. OSF1 A write up on OSF/1 2. OSFVS5R4 A Comparison of OSF/1 vs S5R4 3. OSFGUI A Graphical User Interface for OSF 4. OSF-SMP SMP in OSF/1 5. BINCOMPT Binary Compatibility - A Migration Strategy 6. OSFVALUE The value of OSF to its' members OSF-DCE PACKAGE 1. DCE-RTNL DCE Rational Paper 2. DCE-DESC DCE Description 3. DCE-RPC Remote Proceedure Call in DCE 4. DCE-DIRS Directory Services in DCE 5. DCE-FS File System in DCE TO ORDER ......... IF you are in an Asia Pacific Sth country - use the AIX command to access AIX Bulletin Board, Select MARKETING Menu, Select AIXMKTG CATALOG & PF4 the Package you want to order. If you are in any other country, ..... TOOLS SENDTO SYDVM1 ICTOOLS AIXMKTG GET OSF1 PACKAGE * or TOOLS SENDTO SYDVM1 ICTOOLS AIXMKTG GET OSF-DCE PACKAGE * Doug Marker - AIX Centre, AP Sth, Sydney Australia. ========================================================================= 91091. A comparison of User Interface builders in UniNews Motif-Based GUI Builders Help Developers ======================================== In UniNews May 13, 1991 (Vol. V, No.10) their was a comparison of the GUI builders mentioned above. Here a tabel excerpted from this paper. Vendor Product Avail. Price Std. OSF Dyn. Scrns Real-Time Widgets Data acc. incl. Visual UIM/X 11/90 5 k$ yes yes yes Edge, Montreal Canada ICS Builder 4/91 2.5 k$ yes no no Cambridge Xcessory Mass. Kinesix Sammi 3/91 5-20 k$ yes yes yes Houston Texas JYACC JAM 5/91 1-6.5 k$ yes no no New York By the way, UIM/X has a contract with IBM :-) ========================================================================= 91092. Vital info on the /6000 and how to get it Handy Tuning Ref for the 6000 (from TUNING FORUM on IBMUNIX) How to get ... config, cpu, disk i/o, page i/o, real & virtual storage, disk storage, page storage, ... info, without any special tools. CATEGORY: command option (task (output example CONFIG: uname -m (list model (000003831000 -- 11= mod 540 14= mod 540 1C= mod 550 20= mod 930 30= mod 520 31= mod 320 35= mod 320H 10= mod 530 or 730* * lsdev -Ct hispd3d (nothing=530, else High Speed 3D Graphics Accelerator lslpp -h bos.obj (list history of the base operating system (Release 03.01.0000.0001 -- -- ---- ---- | | | | | | | +- build level | | +------ update level | +---------- release level +------------- version ( Service level 3005 = AIX 3.1.5 = 03.01.0005.???? lscfg -v (list config (i.e. Vital Product Data (lists machine's parts and a description of each CPU: iostat 1 2 (snapshot of cpu ( %user %sys %idle %iowait ( 1.9 2.9 95.2 0.0 (note: sums to 100%, that means no overlap) ps vg (snapshot of user cpu ( UID %CPU CMD ( mes 0.3% ksh DISK I/O: iostat 10 2 (snapshot of device busy ( %tm_act Kbps tps msps Kb_read Kb_wrtn (hdisk0 47.3 92.7 23.0 892 36 (translation: 4k/tps; 21ms/t; 20ms/4k; 89.2Kr; 3.6Kw PAGE I/O: vmstat 1 2 (snapshot of page i/o ( page faults ( -------------------------------- -------------- ( re pi po fr* sr* cy* in sy cs ( 0 0 0 0 0 0 112 13 23 ( ( page page page page page clock dev subs con- ( re- spce spce free scan cyc ints /sec text ( claim page page /sec /sec /sec /sec switch ( /sec ins outs /sec ( /sec /sec ( * page stealing info: ( fr= pages stolen per sec ( sr= pages examined per sec ( cy= revolutions per sec (see: SC23-2365-00 page 7-6 vmstat -s (twice) (delta snapshot of page i/o (note: 100 second delta ending 3:15pm 5/21/91 Tuesday (---------------------------------------------------- ( 728 total address trans. faults ( 585 page ins ( 199 page outs ( 0 paging space page ins ( 0 paging space page outs ( 0 total reclaims ( 91 zero filled pages faults ( 2 executable filled pages faults ( 0 pages examined by clock ( 0 revolutions of the clock hand ( 0 pages freed by the clock ( 1 backtracks ( 579 lock misses ( 0 free frame waits ( 0 extend XPT waits ( 579 pending I/O waits ( 788 start I/Os ( 784 iodones ( 18318 cpu context switches ( 13306 device interrupts ( 700 software interrupts ( 0 traps ( 31915 syscalls (see: SC23-2365-00 page 7-4 ps vg (twice) (delta snapshot of user paging ( UID PGIN CMD ( mes 12 ksh ( -- (cumulative page-ins ... ( includes non-page-space page ins (see: SC23-2365-00 page 7-23 REAL & VIRTUAL STORAGE: lsdev -Cc memory (list total memory ( mem0 16 MB SD1 Memory Card ( mem1 16 MB SD1 Memory Card ( mem2 8 MB SD1 Memory Card ( mem3 8 MB SD1 Memory Card ( ----- ( 48 MB vmstat 1 2 (snapshot of virtual memory, free list ( -- avm 4k -- -- fre 4k -- ( 5142 (20.1MB) 2616 (10.2MB) ps vg (snapshot of user memory ( virt real virt real real ( user data c+d code code stor ( id seg* seg seg seg % command ( in-K in-K in-K in-K ( ( UID SIZE RSS TSIZ TRS %MEM CMD ( mes 100 364 291 264 1% ksh ( *--- also page space size ( note: multiple counting of shared segments (see: SC23-2365-00 page 7-22 DISK STORAGE: lsdev -Cc disk (list dasd ( hdisk0 670MB SCSI Disk Drive (636MB ( hdisk1 670MB SCSI Disk Drive (636MB ( hdisk2 355MB SCSI Disk Drive (336MB ( ----- ( 1608MB lsvg (list vol groups ( rootvg lsvg -p rootvg (list used space (each pp is 4MB ( hdisk0 total pps 159 (636MB) free pps 90 (360MB ( hdisk1 total pps 159 (636MB) free pps 154 (616MB ( hdisk2 total pps 84 (336MB) free pps 79 (316MB ----- ----- ( used = 316MB = 1608MB - 1292MB lsvg -l rootvg (list logical volumes (each pp is 4MB ( lv ----totalMB--- ----TYPE--- mount-point ( hd6 5pps ( 20MB) paging ( hd61 5pps ( 20MB) paging ( hd62 5pps ( 20MB) paging ( hd5 2pps ( 8MB) boot /blv ( hd7 2pps ( 8MB) sysdump /mnt ( hd8 1pps ( 4MB) jfslog ( hd4 12pps ( 48MB) jfs / ( hd2 32pps (128MB) jfs /usr ( hd3 3pps ( 12MB) jfs /tmp ( hd1 11pps ( 44MB) jfs /u ( lv00 1pps ( 4MB) jfs /var ( ----- ( 316MB df (list space ( fs --- totalKB -- -- %used -- mount-point ( hd4 49152 ( 48MB) 83 ( 39.8MB) / ( hd2 131072 (128MB) 95 (121.6MB) /usr ( hd3 12228 ( 12MB) 4 ( .5MB) /tmp ( hd1 45056 ( 44MB) 28 ( 12.3MB) /u ( lv00 4096 ( 4MB) 47 ( 1.9MB) /var ( ----- ------- ( (236MB) (176.1MB) PAGE STORAGE: lsps -a (as su?) (list page space ( hdisk2 size 20MB, %used 24 ( 4.8MB ( hdisk1 size 20MB, %used 25 ( 5.0MB ( hdisk0 size 20MB, %used 56 (11.2MB ( ---- ---- ( 60MB 21.0MB John Messenger ========================================================================= 91093. More disk arrays Disk arrays from Maximum Strategies =================================== (AIXOEM FORUM appended at 15:08:30 on 91/05/23) Maximum Stategies has just announced their disk array subsystem that attaches to the microchannel. The arrays have a transfer rate of up to 18MB/sec and a formatted capacity of 10.8GB - 43.2GB. They will be available beginning July 15th at which time a driver will be available for the RISC System/6000. Maximum Strategies is located in San Jose, CA; the contact there is Wes Meador who can be reached at (408)456-8880. The IBM contact is Mark Seymour on tie line ......... By the way, this company also sells HIPPI connected disk arrays. Shelly/Michele Fisher ========================================================================= 91094. How to recover from a 552 error. If your machine refuses to boot and shows you the LED code 552, than the following procedure might be helpfull for you: Boot with the install and maint floppies (or tape). Go into the maintenance shell. enter sh /etc/continue hdisk0 If this gives you errors, than proceed with /etc/aix/logform /dev/hd8 fsck all filesystems. leave maintenance mode switch the machine off and on again. ATTENTION: logform will reformat the log volume to a default state| Use this method only if everything else fails| ======================================================================== ======================================================================== The IQ of the group is the lowest IQ of a member of the group divided by the number of people in the group. >91.06.06 Table of contents: 91099. A better way to read AIXTIPS NEWS 91100. AIX PS/2 Version 1.2.1 - false installation error message 91101. Xstation marketing guide available 91102. AIX device driver kit from Pencom 91103. TEMPESTED and RUGGEDIZED RISC/6000 systems 91104. Archiving system on Risc System 6000 91105. Getting information out of InfoExplorer ======================================================================== >91099. A better way to read AIXTIPS NEWS Some users requested changes to format of AIXTIPS NEWS for better readability. From now on the table of contents will be visible on the first page. If you view the news with PEEK or browse them with XEDIT, then the EXPNEWS PACKAGE from VMTOOLS might give you a better reading environment. It shows only the lines starting with >. I will mark all headlines with a > so that you can use EXPNEWS to zoom in and out of the news items. If you do not have EXPNEWS XEDIT on your local VM system, you can get it with TOOLS TO VMTOOLS GET EXPNEWS PACKAGE There is also an EXPNEWS FORUM on IBMVM for support questions. ======================================================================== >91100. AIX PS/2 Version 1.2.1 - false installation error message There is an error message during the installation of AIX PS/2 Version 1.2.1 after loading all the operating system diskettes and before the post installation phase. The error message is printed whether installing from diskette or ITBU tape. The message is : 'THERE WERE PROBLEMS INSTALLING AIX FROM THE DISTRIBUTION MEDIA'. This is a FALSE error message. The system continues to post-install and the system works correctly. This occurs only during a stand-alone installation, not installing on a TCF cluster. The problem has been reported and is currently being addressed. Please refer questions to PARHAM at DALVM41B. ======================================================================== >91101. Xstation marketing guide available June 3, 1991 An IBM Xstation Marketing Guide is now available. The guide contains information that should be helpful in developing winning marketing strategies for IBM Xstations. Included in the guide are topics such as features and benefits of the Xstation hardware and software, guidelines for positioning the product as an end-user alternative, ideas on where to sell an Xstation, and offerings from representative competition. It also includes a list of additional sources of information on Xstations. The IBM Xstation Marketing Guide is available electronically as a LIST3820 file, already formatted for a 3820 printer. To obtain the marketing guide, issue the following command from your PROFS command line, or from CMS: TOOLS SENDTO DALVM41B TOOLS AIXIC GET XSTAMG PACKAGE Any questions on this notice should be forwarded to: RHQVM05(MOIST) ======================================================================== >91102. AIX device driver kit from Pencom Pencom Software Inc, Austin, Texas has come out with a low-cost device driver development kit for the RISC System/6000 Unix workstation: the $500 package includes an AIX SCSI kernel extension, the required Object Data Manager configuration methods, an installation procedure using an AIX Installp program and the makefiles necessary to build and configure an AIX 3.1 driver. Contact Pencom at 001-512-343-1111 ======================================================================== >91103. TEMPESTED and RUGGEDIZED RISC/6000 systems In response to a number of inquiries about TEMPESTED and RUGGEDIZED RS/6000 systems, I am distributing the following information to assist you in responding to customer requirements for such products: - There is currently no plan from AWD to make TEMPESTED or RUGGEDIZED RS/6000 models available as standard products. - AWD has established a relationship with HETRA, a business partner in Sebastian, Fl, USA, for the purpose of developing and marketing TEMPESTED RS/6000s. HETRA is currently marketing a TEMPESTED Model 320 and a TEMPESTED Xstation 130. If your country has customers interested in a TEMPESTED RS/6000, contact John Thompson, HETRA Marketing Manager, at phone number (407) 589-7331; OR, submit an RPQ to IBM. - AWD is working on RPQs for RUGGEDIZED versions of the RS/6000. Currently, there is a RUGGEDIZED 320 and a RUGGEDIZED Xstation 130 planned to be available as RPQs in August. To obtain these products, or to request other RUGGEDIZED RS/6000 models, submit RPQs. - Federal Systems Division (FSD) has also developed a number of RUGGEDIZED RS/6000 products, including DASD. To get more information about these products and how to order them or request additional RUGGEDIZED products, contact Pat Noonan in Owego, New York. ======================================================================== >91104. Archiving system on Risc System 6000 Try Q-Star technologies for Optical Juke box. Bethesda, Maryland USA 301-564-6006 Take a look at Intellegent Query for the software: Norcross, Georgia USA 404-446-8880 ======================================================================== >91105. Getting information out of InfoExplorer Some things that I've pulled from the forums, ASKQ, etc.. If you want to put something on tape or diskette use one of methods described below to create a file on disk and then use your favorite command to copy it to the removeable media. Hope it helps, How does one cut and paste text from info documents? ---------------------------------------------------- Several ways : 1. In the windows version you can mark the text that you want to copy by holding down the left mouse button, dragging over the text you want to copy and then release the button. Next, go to the blue menu bar at the top of the window and click on info - click on Copy from the info menu. Now (in another window) start an editor session and go into insert mode. Move the mouse pointer to the editor window and press the middle mouse button. The text that was marked in the info window will now be put into the editor window. 2. If the information you want to copy is a command or a subroutine, issue "man commandname > /tmp/file". This will put all of the text for the command into the /tmp/file (use whatever file you want), then print or change the file. 3. Set up a dummy print queue which spools text to a temporary file instead of a printer. Make this queue the default for your machine (i.e. first listed in /etc/qconfig) or set the value of the PRINTER variable (PRINTER=your_queue;export PRINTER). Then select "print article" from the info pulldown menu. The article will be appended to the file specified in the /etc/qconfig setup. Following is an example of a possible stanza set to be added to /etc/qconfig (Remember that spaces and tabs ARE important, look at the example (*'ed) stanzas as well as the 'real' ones) : info: discipline = fcfs up = TRUE device = dinfo dinfo: backend = /bin/cat file = /tmp/info.out access = write feed = never header = never trailer = never Essentially this is the bit labeled "Example of local print queue configuration" that is commented out in the default /etc/qconfig. All that was changed was the device, backend and file keywords. This queue must either be the default queue (first listed in /etc/qconfig) or must be assigned to the PRINTER variable (PRINTER=info;export PRINTER done in the window that you issue the info command) for the Print Article button to use. Be sure to issue 'enq -A' after you add the above stanzas to make the queue known to the system. The named file (/tmp/info.out in my case) must exist before you try to print an article (use 'touch filename' to create the file). Each time you hit the Print Article button, the text of the article will be appended to the end of the file. Once you have all you need, copy /tmp/info.out to your preferred filename, then empty it (use redirection to empty a file, i.e. '> /tmp/info.out'). Good Luck, Chukk Haselhorst ======================================================================== ======================================================================== OS/2 The nightmare continues ======================================================================== 91.06.06 Table of contents: 91106. AIXDOC Disk Shadow in Dallas. 91107. AIXPERT Publication: spring 1991 edition 91108. CADAM performance on X130 91109. INGRES Performance update on RISC SYSTEM/6000 91110. To which lpp belongs this file? 91111. Tuning hints & suggestions for ORACLE rdbms 91112. 2 new ITSC almost documents 91113. Boot floppies for update 2006 91114. RISC SYSTEM/6000 Mouse Pads can be ordered - SC23-2247. 91115. SERIES/1 migration guides available on the marketing tools disk 91117. Substituting your own library functions 91118. terminfo and login bugs 91119. 6091-23 support on Xstations 91120. RFC for AIXV3.1.5 Telnet 91121. More on Disk Arrays ======================================================================== >91106. AIXDOC Disk Shadow in Dallas. AIXTIPS and AIXTIPS NEWS can now be ordered through a shadow in Dallas. We suggest that American customers use the shadow in Dallas to reduce intercontinental network traffic. First unsubscribe on the master, else you will get the news twice: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC UNSUB AIXTIPS NEWS Then subscribe to the shadow in Dallas: TOOLS SENDTO DALVM41B IBMPC AIXDOC SUB AIXTIPS NEWS ======================================================================== >91107. AIXPERT Publication: spring 1991 edition AIXpert Publication: Spring 1991 Edition Now Available from Mechanicsburg June 7, 1991 The Spring edition of the AIXpert, a quarterly publication for AIX software developers is now available. This issue focuses on RISC System/6000 porting, and includes two articles by Gary Andrews which provide a wealth of useful tips and techniques on the porting process. The Software Vendor Technical Support Center in Dallas has contributed a list of twenty frequently asked technical questions and answers. And this issue's executive interview is with Donna Van Fleet. Software vendors may subscribe to this publication by calling the Software Vendor Information Line at 1-800-627-8363, or by completing the insert card in the Winter or Spring issue. IBM employees may order this issue from Mechanicsburg using order number G580-0006-00. Or you may subscribe to this publication using SLSS (System Library Subscription Service) and specifying form number GBOF-1199. (SLSS may be accessed from HONE. If you do not have access to HONE, you can obtain an SLSS form from a branch office.) If you have questions or comments you may contact the editor, Gloria Hardman - RHQVM21/HARDMAN. ======================================================================== >91108. CADAM performance on X130 CADAM is a pixmap application, and pixmaps load the network down a lot. One thing we found that can help the network problem is that the send and receive buffers for RIOS are set at 4K and the buffers in the Xstation are 8K. You can get greater efficiency by making them equal. Enter the following command on the RISC system: no -o 'tcp_sendspace=8192' This will increase the network performance 10-20%, which affects high transfer rate items such as pixmaps and CADAM. Note, the /etc/no program is not available before 3003. ======================================================================== >91109. INGRES Performance update on RISC SYSTEM/6000 Recently Ingres and IBM spent several days at IBM Austin as part of the IBM Performance Tuning Program. The result of this joint effort was the identification of areas for tuning which have generated significant overall performance improvement. Among the areas identified and addressed were default settings, log buffer sizing, and memory resource allocation. These issues offer immediate solutions and Ingres has implemented a new patch release to address them. The most recent Ingres product has now been optimized for 90 percent of the INGRES code and provides substantial performance improvements. Both Ingres and IBM are continuing work on other areas with long-term performance potential, such as the compiler/optimizer issue and the Test and Set instruction. Comparison testing with identical INGRES applications running on similarly configured SUN4, Solburne and RISC System/6000 platforms show the RISC System/6000 outperforming the competitors. Ingres and IBM can be confident that the Ingres-for-RISC System/6000 product offers our customers a very competitive and workable solution for their application development and database server needs. In summary, the recent work done jointly by IBM and Ingres to identify, understand, and resolve key short-term performance issues has been a success. Both companies are committed to continue efforts to achieve additional performance improvements. For performance related technical information, call Barbara Strunk at (203) 783-7053 or tie-line 571-7053 or Jim Gammon at (415) 748-3614. For general information on Ingres products, call 1-800-4-INGRES (1-800-446-4737) ======================================================================== >91110. To which lpp belongs this file? #|/bin/sh # # shell script to tell you which "lpp" a given file or directory belongs to # syntax: whichlpp path # # For more information, see InfoExplorer and odmget, odmshow, inventory. # -Mickey Coggins for FILENAME do odmget -qloc0=$FILENAME inventory egrep "lpploc0" sort cut -d= -f2 paste - - done Save it somewhere in your path (like /usr/local/bin) Then try for example whichlpp /usr/bin/dc /usr/bin/X11 ======================================================================== >91111. Tuning hints & suggestions for ORACLE rdbms ORACLE EUROPE ENGINEERING DIVISION - MAY 1991 INTRODUCTION This document contains tuning tips for ORACLE version 6.0.31 on the IBM RI System/6000 (3), as well as some hints, suggestions and other information. hope to make this an evolving document, so YOUR feedback is very welcome. The IBM RISC System/6000 with AIX 3.1 is not very special with respect tuning when compared to other UNIX (and non-UNIX) systems, and you shou always use the general tuning hints in the ORACLE RDBMS Performance Tuni Guide (1). Some points below are general hints. If you have any valuab input to this document, please communicate them to us (names below). The use of raw devices as described in this document is supported when usi Oracle release 6.0.31.0.5 or later and AIX 3.1 with the 3003 update or later TUNING ORACLE ON AN IBM RISC SYSTEM/6000 Tuning Oracle is done via the startup parameters (or init.ora parameters), s (2) for a complete description of the various parameters. o If you use raw devices or your application does intensive changes to t database (insert/update/delete), you should make the SGA as big possible, in particular the db_buffers, keeping the paging activity zero or an absolute minimum. If your application is doing mostly selec from the database and is not using raw devices, it is not alwa beneficial to use a large SGA. The reason for this is that the AIX fi buffer cache will be used to fulfill read-requests from Oracle to t operating system. o Make sure the redo-logs are on a separate drive, so the sequential writ to them can be done without head-movements. o Spread the db-files on the available disks, and use a number of db_write at least equal to the number of drives with db-files. Make sure t logical volumes containing the db-files are on contiguous physic partitions. o Use IOSTAT/VMSTAT to verify that the disk load is properly spread ev among the disks. o When running with multiple db_writers, the db_block_write_batch paramet should be increased since the latter sets the total batch size, and n the batch size per db_writer. o Since the AIX file system has a 4k block size, using 4096 byte ORAC blocks (startup parameter db_block_size in init.ora) will give the be performance. Please note that the default is 2048 bytes. Also refer the notes below about block sizes on raw devices. RAW DEVICES In order to get the best performance with raw devices, you should follow the guidelines: o Raw devices are setup as logical volumes using SMIT. It is suggested specify a logical volume name, e.g. 'lvoracle1', 'lvoracle2' , etc. distinguish these from logical volumes that contain file systems, et After creating the logical volumes with SMIT, exit SMIT and make yo Oracle user owner of the special files in /dev, e.g.: # chown oracle /dev/lvoracle1 /dev/rlvoracle1 o Raw devices are considered by Oracle to have 512 byte physical blocksi if the character device (e.g. /dev/rlvoracle1) is used, and a 40 physical blocksize if the block device (e.g. /dev/lvoracle1) is used. T physical blocksize is used for two purposes by Oracle; it is the size the redo log files, and the block size of the database files must multiple of it. Regular files are considered as having 512 byte physic blocksize. o If performance is your main concern, you should use the block devices a a 4096 bytes blocksize for all your database and redo log files. o When using raw devices as database files, you should use an Oracle blo size of 4096 bytes and use the block special device as the database fi name (e.g./dev/lvoracle1). The default Oracle block size is 2048 bytes. You can use smaller blocksizes than 4096 bytes by using the charact special file (e.g. /dev/rlvoracle1). It is advised not to mix regular files, character special, and blo special devices for database files. o If you put redo log files on block special devices, the block size will 4096, which can cause more redo waste. This is particularly true updates to your database are very small and/or infrequent. Either all or none of the redo logs must be block special devices, a mixing of regular file and character special devices is not allowed. o AIX file buffer cache is not used with raw devices. Since the AIX buff cache can be used to fulfill read-requests when regular files are use you should compensate for the missing AIX buffers by increasing yo Oracle buffer cache (init.ora parameter db_buffers). o To increase full table scan performance, set use_readv to true. Th parameter is not documented in the first edition of the Installation a Users' Guide. USING THE LOGICAL VOLUME MANAGER AND RAW DEVICES Though Oracle uses the AIX file system, it also uses the Logical Volu Manager (LVM), which is the tool found in AIX 3.1 for the handling of physic and logical file storage. When seen as an operating system facility, the LVM is transparent to Oracl which uses the LVM to handle the files or the raw devices that make up t database. When seen as a resource, the correct setup of the LVM is important as it c impact performance and safety. To achieve the maximum possible performance, you should be sure to use the L in a way that minimizes disk head movement. The key issues here are: o Logical volumes with Oracle database files and Oracle control files a read and written randomly, and should consist of contiguous physic partitions. The RDBMS processes can write to multiple files at one tim therefore logical volumes should not be spread over more than one physic volume. It is far better to have multiple logical volumes, each being raw device, or a filesystem volume with one (or more) database files. o Under normal operation, logical volumes with Oracle redo log files a only written sequentially. Placing redo log files on logical volumes th consist of complete physical volumes will significantly decrease the di head movement on this physical volume. You can split the physical volu into a number of logical volumes, each being used as a raw device, or y can create one logical volume with a file system. o Disk mirroring can be used to improve safety in case of power or di failures, system crashes, etc. It should be noted that Oracle has its o means of providing a similar safety function that works by: - Placing multiple copies of the control-files on separate physic partitions. - Archiving redo log files on external media. - Using write-through-cache. The RDBMS always waits for a wri operation to complete before continuing. If you consider using disk mirroring, it can best be implemented on t logical volumes that contain the redo log files only. The Oracle RDBMS kee its own copy of the control files on multiple disks. These files and an (ol backup of the database files plus archived and current log files a sufficient for a recovery. For further information, please see the ORAC RDBMS Database Administrator's Guide (2). INSTALLATION HINTS On some occasions, the file /etc/inittab has been corrupted duri installation of Oracle, in particular if the Oracle installation scripts ha been executed a second time as the root user. In order to be able to recov from the loss of the /etc/inittab file it is suggested to make a copy of before installing Oracle. This can be done by: # cp /etc/inittab /etc/inittab.bak as root. In the event that the /etc/inittab should be destroyed, it c easily be recovered by booting your system in single user mode and copying t backup back to the original filename. READING 8MM TAPES 8mm tapes require the block size of the tape device to be 1024K. The defau is 512K so you will need to change this using SMIT. To do this, login to SM and follow the path below: Devices Tape Drive Change / Show Characteristics of a Tape Drive (Select the appropriate tape drive) BLOCK size (0=variable length, change this value from 512 to 1024) AUTOMATIC STARTUP OF THE DATABASE AT SYSTEM STARTUP During installation, Oracle makes the entry below in the /etc/inittab file: orapw:2:once:/etc/loadext /etc/pw-syscall This entry will load the post/wait driver into the AIX kernel. It essential that this is done before Oracle can be started. The second editi of the Installation and User's Guide describes a way to automatically execu the dbstart script during system reboot, by adding another entry to t /etc/inittab file. Another way of doing it is by adding the call to dbstart to the /etc/rc fil Since the kernel extension must be in memory when Oracle is started, th means that the above entry must come before the call to the rc file. T order should be as follows: brc::sysinit:/etc/brc >/dev/console 2>&1 # Phase 2 of System boot orapw:2:once:/etc/loadext /etc/pw-syscall rc:2:wait:/etc/rc > /dev/console 2>&1 # Multi-User checks You can then add the line: su oracle -c /...oracle_home_path.../bin/dbstart to the /etc/rc file and all databases with an 'N' in the third field of t /etc/oratab file be started during system boot. For additional informati regarding the post/wait driver please see the separate section below. RUNNING ON LEVEL 3003 OR LATER OF AIX If you are running on level 3003 or later of AIX, it is recommended that y always relink your executables. This is done if you give a positive reply the installation question of customizing the installation. POST/WAIT KERNEL EXTENSION FOR IBM RISC SYSTEM/6000 AIX 3.1 provides software developers with the standard set of operating syst calls present in any implementation of UNIX. AIX 3.1 also contains an ext set of system calls, so called kernel extensions. IBM provides these kern extensions to allow the addition of hardware devices that require speci handling. System facilities at a lower level than provided by the norm system calls can be used to support such devices. These give softwa developers much more possibilities than are found at the system call level. Oracle requires means of communicating between the RDBMS kernel processes a the shadow processes. Simply, a background process may need to write datablock to disk and it therefore posts (requests) the database writer perform this function. The background process waits until the database writ has written the datablock and posts (advises) the shadow process to resume i work. This is a frequent operation between the RDBMS and the operating syst kernel. In most implementations of Oracle on UNIX systems, this is done usi the UNIX semaphores. Relatively, semaphores are a slow process and a improvement made in the posting and waiting for the request and advice makes significant improvement in performance. Thus a small percentage improvemen or fewer instructions used in this process reduces the total load on t system. In Oracle on AIX 3.1, the performance of the posting and waiting is improv by replacing the semaphore calls by use of the IBM provided kernel extensio that perform a similar task. The kernel extension is an interface between t RDBMS processes and the AIX low level kernel services. In the Installati and User's Guide for the IBM RISC System/6000 it is called the post/wa driver. EPILOGUE Please send your updates and comments to the following people (If you a within Oracle): Bjorn Engsig (bengsig), Joe Gallagher (jgallagh), Bert Simonis (bsimonis Herbert van den Bergh (hbergh), Lisa Borden (lborden). This document is maintained by Bjorn Engsig. If you are outside Oracle, please send comments to: Joseph Gallagher RISC System/6000 Porting Team Leader Oracle Europe Maretimo Court, Temple Road Blackrock, Co, Dublin Ireland Fax 353-1-2834732 or by E-mail to Internet address bengsig@oracle.com REFERENCES ORACLE RDBMS Performance Tuning Guide, Version 6.0, Part No. 5317-V6.0 ORACLE RDBMS Database Administrator's Guide, Version 6.0, Part No. 3601-V6.0 ORACLE for IBM RISC System/6000 Installation and User's Guide, Version 6.0 Part No. 5687-V6.0 TRADEMARKS IBM is a registered trademark and RISC System/6000 and AIX are trademarks the International Business Machines Corporation. UNIX is a registered trademark of UNIX System Laboratories, Inc. Oracle is a registered trademark of Oracle Corporation. Latest update: 25-Apr-91 ======================================================================== >91112. 2 new ITSC almost documents There two ITSC documents that are now available in their final draft versions on AIXTOOLS they are a printing document and an X.25 cookbook. They are named PRNT4FNP and X25COOKB respectively. Use them in good health ...... Mark Johnson ======================================================================== >91113. Boot floppies for update 2006 Be carefull with update 2006: If you have applied update 2006 then the creation of a bos boot floppy is no longer possible| Use the boot floppies that you created with Update 3005. ======================================================================== >91114. RISC SYSTEM/6000 Mouse Pads can be ordered - SC23-2247. June 18, 1991 Field feedback has indicated that our competitors in the workstation marketing area are very effective in providing customers with "promotional" items that advertise their products. We've been asked to consider a way in which our field marketing force can easily order similar items. We created a "mouse pad" that advertises the RISC System/6000 with a colorful Hagar cartoon. It has been used at several trade shows and has been very popular. The mouse pad is 7 by 9 inches, and is made of a "coaster like" material (cork back laminated to hardboard) and works well. This item can now be ordered from Mechanicsburg using PUBORDER. The order number is SC23-2247. If you need a large quantity of this item (over 50), I can put you in touch with the vendor. The vendor also has plastic "luggage tags" with similar art work. These would not be economical to stock in Mechanicsburg, but in quantity, you can also get these from the vendor at reasonable cost. It is not our intent to stock several items this way, but rather, to provide a popular item that effectively accomplishes the objective, and can be functionally useful to the customer. Please direct any questions or comments to: Frank Caldarola at AUSVM6(FRANKC). Thank you. ======================================================================== >91115. SERIES/1 migration guides available on the marketing tools disk June 17, 1991 ZZ30-4055-01 Series/1 Migration Marketing Guide G326-0054-01 Series/1 Migration Planning Guide These Series/1 Guides are now available on the Marketing Tools Disk, and are no longer available from Mechanicsburg in hardcopy. You can request a copy of the guides using the following input: TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET SERIES1 PACKAGE and print out a copy on your branch laser printer. SERIES1 PACKAGE consists of the following: SERIES1 PACKAGE - contains owner name, and file names SER1MKTG LIST3820 - contains information to assist account teams with Series/1s in their territory to understand the Series/1 marketplace, and the migration options available to migrate Series/1 applications to another IBM platform. SER1PLAN LIST3820 - contains information to help Series/1 customers understand the migration options available to assist them in migrating Series/1 applications to another IBM platform. SERIES1 ANNOUNCE - contains guide abstracts. 09/17/91 ======================================================================== >91116. Device driver Redbook GG24-3629 : Writing Device Driver for AIX V3 is now available from Mechanicsburg. There is also a companion package containing all the samples in the book, packaged in an "installp format" (RICDD PACKAGE on AIXTOOLS). Have fun | Luc Smolders ======================================================================== >91117. Substituting your own library functions Since I think I successfully overloaded malloc in libc.a I will post the procedure to aid others along this path. The process is non-obvious. If just linked the Andrew malloc with my application strange behavior occurred. I think this is because I had two version of malloc being used, one for my application calls and one for malloc calls from libc functions. I got the information from comp.unix.aix usenet postings by David J. "Shaggy" Kleikamp and Marc Auslander. I hope this procedure will appear in future documentation. 1. Copy /lib/libc.a to a working directory, make it writeable 2. Extract shr.o from libc.a; ar x ./libc.a shr.o 3. mv shr.o shr.o.orig 4. Create a libc.exp from shr.o.orig dump -Tv shr.o.orig | awk '$4 == "EXP" {print $8}' > libc.exp 5. Create a new shr.o ( replace {your files} with malloc.o ) ld -bh:4 -D0 -bnso -H512 -T512 -bM:SRE -o shr.o {your files} shr.o.orig \ /lib/libs.a -bI:/lib/syscalls.exp -bE:libc.exp -bE:/lib/syscalls.exp 6. Replace shr.o in your working copy of libc.a; ar rv ./libc.a shr.o 7. Set the LIBPATH environment variable to point to your working directory LIBPATH=mydir:/lib:/usr/lib where mydir contains the new libc.a 8. Relink your application using your newly created libc.a Editors note: Sorry for not mentioning the author, but her/his name got lost in the editing process, I do not even remember from which forum/newsgroup it came. ======================================================================== >91118. terminfo and login bugs I've submitted these via normal channels, but this may help someone out there. Problem #1- terminfo problem for 3151s when used with ORACLE Severity- 4 (workaround done) AIX level- 3003 and 3005 both have this problem When using ORACLE, text appears in boxes. If SMIT or vi is invoked, and then ORACLE is used, the boxes no longer show. By teeing the output of vi to a file, I found an invalid command sequence being sent to the 3151. The Sequence is "ESC > B" (sequence is inside quotes). The sequence is not valid according to the 3151 Reference manual (GA18-2634). Valid sequences are "ESC > A" or "ESC >@". I have modified the ibm.ti file by finding all the "\E>B" sequences in the terminfo entry for ibm3151, and changing them to "\E>A". All applications tested (SMIT, vi, ORACLE) now work correctly. It seems that by issuing the "ESC > B" command, the 3151 is being told to select an invalid character set, and it is ends up with a "null" character set for the "extended" characters (which normally include box characters). ======================================================================== Problem #2 Customer- Kaiser ENgineering Severity- 4 AIX level- 3003 and 3005 both exhibit this problem If a user logs in using uppercase (i.e. with capslock on), the system recognises this, and prints out P/A/S/S/W/O/R/D: The user enters a password in uppercase so the login fails. The system then does not allow the login, and asks for the "login:" again. Notice that AIX no longer looks like it is in "uppercase" mode, otherwise it would have said "L/O/G/I/N:". The user then switches caps lock off, and enters root in lowercase. As there is no password on this system, they are logged in BUT the system is still in uppercase mode (ie all lowecase letters are flagged with a /). This means that they have logged using a lowercase userid, but the system has placed them into uppercase mode, which causes the terminal to lock in programs like SMIT. The solution is to modify the login program so that it resets from uppercase mode to lowercase mode each time the "login:" prompt is issued, and only reenters uppercase mode if the userid supplied is in uppercase. --------------------------------------------------------------- Indulis Bernsteins Perth Phone: +61 9 3276870 Advisory SR West Australia Fax: +61 9 3213334 --------------------------------------------------------------- ======================================================================== >91119. 6091-23 support on Xstations Someone asked the question a while back about 6091-23 support for the Xstations. There is now and RPQ for the 6091-23 which allows you to connect it to the Xstation(s). The RPQ number is 8K1744, and the details are available under the "RPQ" application on HONE. This RPQ is basically the same as the RPQ for the 5081 support. Don Ferndelli AIX Tech Support - Dallas ======================================================================== >91120. RFC for AIXV3.1.5 Telnet According to my information, dated 3/7, TELNET complies to: MIL STD 1782 (TELENET) RFC 854 for Protocol Spec RFC 855 for Opt Spec RFC 856 for Binary Transmission RFC 857 for Echo Opt RFC 858 for Suppress Go/Ahead RFC 860 for Timing Mark RFC 1073 for Window Size RFC 1091 for Terminal Type Brice Wolford ======================================================================== >91121. More on Disk Arrays I've got some more informations from Maximum Strategies about their RAIDs. The promised me to send more detailed descriptions. When I recive them, I'll post it here, so that you can obtain copies if you are in need ( not just curiosity |) for RAIDs. Here I'll post what I've got. Strategy RS/6000 RAID Storage Servers ------------------------------------- The Strategy StorageServer Series incorporates innovative RAID technology and takes advantage of the increasing capacities, reliability and cost effectiveness of standard, field proven 5 1/4"rigid disk drives. The Maximum Strategy RAID architecture increases both sustained data transfer rates and capacity by storing and retreiving data from disks in parallel. In addition to the data drives, each bank is configured with a parity drive for fault-tolerant operation. The Storage Server monitors all disk drives for errors and provides on-the-fly parity replacement. An optional hot standby drive is available for immediate replacement. Technical Data ______________ MCP MCR Number of Drive Banks 1 1 to 4 Formatted Capacity 10.8 GB 10.8 to 43.2 GB (Drive dependent) Host Interface Micro Channel Maximum Number of 2 5 Host Interfaces Disk Drive Interface ESDI Transfer-Rate 18 MB/sec (Drive Dependent) Error Correction/Detection 48 Bit polynomial per 1024 Bytes Data Protection Parity & Standby Drives Dimensions (inches) Height 14 70 Width 19 25 Depth 33 41 (MCP is a 19" drawer, MCR a complete 19" rack) Maximum Strategy SFX Filesystem ------------------------------- The Staretgy SFX Filesystem provides directory and file management of storage for the Startegy Storage Server Series. The SFX fielsystem draws upon the strengths of the Unix filesystem, sharing a similar hierarchical directory structure and file access techniques. The SFX filesystem also provides contiguity of file data on disk, allowing very large continous disk transfers. The SFX filesystem tree may be composed of multiple partitions, each with its oqn independent, user definable block size. Also files are not limited to 4 GB as in Unix. The SFX Filesystem product consists of the following components: * User and Administrative Utility commands * Subroutine library including "C" source * Maintenance commands * Unix-style manual pages From the command level the SFX filesystem provides the following commonly used user and adminstrative commands: sfcp - copy to and from SFX filesystem sfdf - report disk usage of an SFX filesystem's partitions sfls - .... sfmkdir - .... sfmv - ... sfrm - .... sfrmdir - ... sfck - check consistency and repair an SFX filesystem sfmkfs - ... A complete subroutine library (with "C" source) is available for calling from user-developed application programs to performoperations on the SFX filesystem. Calls such as sfopen, sfwrite, sfread, and sfclose are very similar to standard Unix system calls. Caveat lector ------------- The MCP and MCR RAId Sorage Servers are designed for high performance storage applications. They are not intended for use as a system disk. The server may have multiple host connections. These are completely independent connections. the only thing that the user must be aware of when using multiple host interfaces is taht there is no internal protection in regard of to filesystem consistency. For reading data from the server this is not a problem. However, if both hosts are writing data to the server, there must be some external communication between the hosts to protect writing and reading the superblock. H. Backhausen ======================================================================== ======================================================================== Old programmers never die. They just branch to a new address. Hello, this is AIXTIPS NEWS, an additional service from the AIXTIPS group. BEWARE| This file has to be treated as IBM CONFIDENTIAL| >91.07.17 Table of contents: 91122. Vacation 91123. SNAFLOW package 91124. Redbook: Printing for Fun and Profit Under AIX V3.1 (GG24-3570) 91125. Microchannel adapter catlog 91126. More than two external SCSI devices on the internal SCSI adapter 91127. IBM Client/Server handbook draft on mkttools 91128. AIX Version 3 source code available 91129. A comparison of AIX XL FORTRAN versions 2.1 and 2.2 91130. PAIX for AIX/370, a multiprocessor AIX 91131. Xhibition '91 91132. Connecting Nixdorf Printer ND49 to RISC/ 6000 ======================================================================== If you need older issues of AIXTIPS NEWS you have to request the newslog: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWSLOG Older news logs are avaliable in tersed format. For 1990 use TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWS90T and then unTERSE the received file. If you got this file as a copy and want to have any future versions sent to your reader automatically use the command: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC SUB AIXTIPS NEWS If you view this file with XEDIT or PEEK it from your readerlist, try the EXPNEWS command. It will present only the headlines of the articles and you can zoom in and zooom out like with an outline system. have fun AIXTIPS at MUNIVM4 ======================================================================== >91122. Vacation AIXTIPS was on vacation the last three weeks. We now will continue with our regular sporadic service :-) ======================================================================== >91123. SNAFLOW package Dallas has recently developed an internal use only tool to aid in the decoding of Risc System/6000 SNA trace information. This tool is internal use only, but the output is designated as non-confidential and so can be left with your customers. The tool - called SNAFLOW - is available from a tools disk in Dallas. To extract the tool along with limited documentation use the command in CMS: tools sendto dalvm41b tools aixic get snaflow package Note that this package is only support in the United States. No support is available for EMEA or APG countries. The tool should be used as an aid to problem determination - but it is in no way supported either from a defect or a non-defect. Please be aware of these limitations if you plan to extensively use SNAFLOW. Regards - Mark Jones ======================================================================== >91124. Redbook: Printing for Fun and Profit Under AIX V3.1 (GG24-3570) A final draft version of the redbook, Printing for Fun and Profit Under AIX V3.1 (GG24-3570) has been placed on the AIXTOOLS disk. This is a final draft of the redbook that will become available later this year. It is designed for SEs and customers with general levels of AIX and UNIX skills to help them perform the most common printer related tasks. The document also attempts to explain how AIX manages printing and printers. To access, use TOOLCAT AIXTOOLS .... if the AIXTOOLS catalog is kept up to date locally. Or alternatively, you may use the command: EXEC TOOLS SENDTO YKTVMV TOOLS AIXTOOLS GET PRNT4FNP * Good lucK||| Mark Johnson ITSC Austin MARKJOHN at AUSVM8 ======================================================================== >91125. Microchannel adapter catlog NEW EDITION OF ADAPTER CATALOG AVAILABLE July 8, 1991 The 7th edition of the CATALOG OF INTERNATIONAL MICRO CHANNEL EXPANSION ADAPTERS is being released into Mechanicsburg as IBM Form #G360-2824-06. This document contains information about expansion adapters available from IBM as well as Independent Option Vendors (IOVs) from 24 countries around the world supporting IBM* Micro Channel* architecture-based systems: PS/2* computers, RISC System/6000* POWERstations and POWERservers and Micro Channel* 370 models. The expansion adapters are presented in 2 parts, those from IBM and those from IOVs, and each expansion adapter is listed alphabetically under the category heading that best describes its function. All of the information presented for each expansion adapter has been certified as accurate and up to date by an authorized representative of the manufacturer prior to being included in this edition. Part 3 on pages 155-159 presents information and phone numbers to assist potential developers of expansion adapters around the world in obtaining the necessary documentation and assistance to support the IBM Micro Channel architecture-based systems. *Trademark of the IBM Corporation. Questions on this notice may be forwarded to BCRVM5(MILI). ======================================================================== >91126. More than two external SCSI devices on the internal SCSI adapter A previous news entry allready mentioned this function. Now it is also available in EMEA. Replace the internal SCSI cable and the external SCSI terminator if you want to attach more than two external devices on an internal SCSI adapter. The par numbers are: 00G0963 and 00G0968 Volker Kuhm ======================================================================== >91127. IBM Client/Server handbook draft on mkttools The IBM Client/Server Handbook provides an understanding of the breadth of Client/Server Computing and IBM's support. It is an 'IBM Internal Use Only' document that has been helpful to field and HQ people even in draft form. Be sure to read the introductory remarks before using. The Handbook is a 155 page FOILS5 document with sections on: Client/Server Computing and Related Concepts IBM Position, Client/Server Support, and Sales Strategy Common Issues: Client Selection, Server Selection, Database and Applicatio ns RPC and APPC, OSF DCE, DAE, Open Systems, Software Distribution, Problem/Performance Management, Application Development, Network Support IBM Server Platforms: PS/2, RISC System/6000, AS/400, ES/9000 Retrieve the Handbook with the following command: ex tools sendto bcrvmms1 tools mkttools get cshandbk package CONTACT: Micks Purnell, Client/Server Marketing, White Plains NY 8-351-3279, RHQVM04(MICKS) ======================================================================== >91128. AIX Version 3 source code available Source code for AIX Version 3 for RISC System/6000 is now available, as announced July 2, 1991, in letter 291-335 on HONE. The source code is provided as a non-standard PRPQ (P91084). It is intended for customers such as colleges and universities, research labs, and government agencies who require source code for their own internal business purposes. In addition to the announcement letter and PRPQ description, a question and answer package is available electronically, to help you better understand and position this announcement. To request the Qs&As, already formatted as a LIST3820 file, key the following on your PROFS command line, or in CMS: TOOLS SENDTO DALVM41B TOOLS AIXIC GET SOURCEQA PACKAGE This is currently for the US only. ======================================================================== >91129. A comparison of AIX XL FORTRAN versions 2.1 and 2.2 This document is intended to explain to you or your customer the differences in AIX XL FORTRAN Versions 2.1 and 2.2, the corresponding performance benefits and what type of applications will benefit. The document is organized as follows : 1. Introduction to Pre-Processors 2. AIX XL FORTRAN Version 2.1 3. AIX XL FORTRAN Version 2.2 4. Performance and Size Comparisons 5. Conclusion In addition to technical explanations of the various optimizations that are done, the document uses performance comparisons based on the FORTRAN benchmarks in SPEC Suite 1.2 to show what types of applications may gain in performance by using these pre-processors. There are two versions included in the package, FORTCUST is the customer level version and FORTINT is the IBM Internal Use Only Version. This package may be obtained via the following command : TOOLS SENDTO DALVM41B TOOLS PEC GET FORTRAN PACKAGE Please send any comments or questions to DALVM41B(PEC). ======================================================================== >91130. PAIX for AIX/370, a multiprocessor AIX One possible solution to the problem of running AIX on a multiprocessor 4381 or 3090 is to run a PAIX, an multiprocessing version of AIX/370. PAIX provides several enhancements to AIX/370 including: - multiprocessing support: a single copy of PAIX supports up to 32 processors running on VM. - X-store support: a device driver that enables PAIX to page to Xstore - enhanced paging subsystem: improved paging algorithms and a multi- level paging system for paging to Xstore and disk with migration. - enhanced CPU scheduler: PAIX includes the Univ. of Maryland scheduler for improved interactive response when running with a mix of interactive and CPU bound jobs. - 2 GB user address space: on processors that have ESA hardware support, PAIX provides a full 2 GB address space for user processes. - asynchronous I/O support: asynchronous event notification and async I/O based on Draft 9 of the POSIX 1003.4 standard. - SNMP - Simple Network Management Protocol - The popular TCP/IP protocol for managing networks is implemented in PAIX. An SNMP Daemon accesses TCP/IP variables in the kernel and makes them available to management programs. - C2 Security - Two changes to the PAIX kernel were implemented to move towards a C2 environment. The first, journals Open system calls, creating an audit trail of "object" usage. The second, "cleans" off a file when it is erased. PAIX maintains binary compatibility with AIX/370 1.2.1. It is installed as an LPP on AIX/370 1.2.1. PAIX is currently in use at several IBM customer locations. It is also running at a couple of IBM internal locations. PAIX was developed at the IBM Scientific Center in Palo Alto. Papers describing the system have been published in the Unite '89 and '90 proceedings. These papers are available via REQUEST from PAIXSUPP at PALOALTO: REQUEST PAIXINFO from PAIXSUPP at PALOALTO The work on SNMP and security was done at the IBM T.J. Watson Reseach Center. Information is available from userid aixhelpaixproj.watson.ibm.com If you think PAIX might be a solution to your mainframe computing problems please send me a note describing your environment and needs. We are investigating the possibility of making PAIX available to IBM internal sites on an "as is" basis with minimal support. Those customers who need a fully supported PAIX must go thru the PRPQ process to obtain PAIX. ======================================================================== >91131. Xhibition '91 The following should be of interest to SE's who are involved with AIXwindows. On June 3-6, 1991, I attended Xhibition, the annual business show focussing on the X window System. Present at the show were all the major Unix system and applications vendors. The two points that struck me the most were the number of companies offering interactive design tools (IDT), for interactively building graphical user interfaces, and the fact that there were IBM RISC System/6000s in 9 other vendor's booths and Xstations in 2 others. The latter situation is a big change over the situation at Xhibition last year| The interesting thing about an IDT is that it enables a user to interactively design and view an application's graphical user interface. In the case of some of these tools, a programmer can also interactively build, test and debug the underlying application code. The system vendors demonstrating IDT's included: SUN, DEC and HP. IBM had a "technology demonstration" of AIXwindows Application Interface Composer (AIC), which is a port of an advanced version of Visual Edge's UIMX. The software vendors demonstrating IDT's included: ICS (Builder Xcessory), TeleSoft (TeleUse), Neuron Data (Open Interface), Non Standard Logics (XFaceMaker 2). All of these are ported to the RISC System/6000 and can be used to generate OSF/Motif compliant interfaces. The differences among them come in what kind of code they generate. This runs the gamut from generating pure C code with X and/or Motif calls to UIL to some proprietary metalanguage. Another interesting technology being demonstrated was platform-independent interface design tools. The two notables here are XVT (XVT Software) and Open Interface (Neuron Data). Both of these provide a toolkit that can be used to build a single source that can ported to the following environments: OSF/Motif, Open Look, Presentation Manager, Windows 3.0, Macintosh, DECwindows (Open Interface only) and character screens (UNIX or DOS, XVT only). Open Interface includes an IDT and XVT Software told me they expect to have one soon. The most notable difference between these two products is that XVT builds its API on top of the native toolkit, whereas Open Interface uses its own, proprietary toolkit. The IBM booth had a number of interesting "technology demonstrations". In addition to AIC (mentioned above), they were demonstrating both X server and X client support on OS/2, PEX (PHIGS Extension to X), and the Paper-Like Interface, using an X server running on the LCD display of a tablet computer supporting handwriting recognition and menu selection using a pen/stylus. Another interesting product being shown in the IBM booth was Frame Maker 3.0, the latest version of that product, which Frame is not yet shipping. In addition to interesting "technology demonstrations" and a presence in other vendors' booths, IBM was well represented with speakers on a number of technical topics. Another sign which I found very encouraging was that as I visited various booths and asked about whether or not a particular software package was ported, or being ported, to AIX, many times the response was "yes" Several vendors even told me that their plans for porting to AIX were going to be moved up due to the large number of customers who have expressed an interest in a port to the 6000. Paul Lugo, ITSC Austin ======================================================================== >91132. Connecting Nixdorf Printer ND49 to RISC/ 6000 There are several thousands of Nixdorf Computers NX 8870 ready to be replaced by our machines. Connected to them are often ND48 / ND49 needle printers. SNI tries to move these users to their MX machine by contending that only they are able to connect the Nixdorf printers to a UNIX machine. To counter this argument I tried to connect an ND49 to our RISC/ 6000. It proved to be very easy. There are but a few things one should know: 1. If the serial interface is installed in the printer, the parallel interface cannot be used (although there is a dip-switch for choosing between parallel and serial interface|||). 2. Configure the printer as "other" serial or parallel printer. 3. During boot time the printer must be turned of for some unknown reasons. Otherwise the boot process will be blocked. Dr. Gerhard Hoffmann, AIX FSC Munich (HOFFMANG at MUNIVM4) ======================================================================== ======================================================================== My boss just told the quote-of-the-day(TM) after talking to our friendly IBM salesguy who said: "You've got be careful about getting locked into open systems" Heh! Why don't I trust these people? :-) This is a life citation from a customer! Not a joke! >91.07.26 Table of contents: 91133. /6000 FAX solutions in Germany 91134. Changing the maximum number of processes / windows 91135. Updated Performance Information 91136. 5080 Emulator for the RISC System can now be ordered 91137. New books on Computer security from O'Reilly 91138. VT100 emulation on th /6000 under X 91139. New AIXTIPS release is coming ======================================================================== If you need older issues of AIXTIPS NEWS you have to request the newslog: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWSLOG Older news logs are avaliable in tersed format. For 1990 use TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWS90T and then unTERSE the received file. If you got this file as a copy and want to have any future versions sent to your reader automatically use the command: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC SUB AIXTIPS NEWS If you view this file with XEDIT or PEEK it from your readerlist, try the EXPNEWS command. It will present only the headlines of the articles and you can zoom in and zooom out like with an outline system. have fun AIXTIPS at MUNIVM4 ======================================================================== >91133. /6000 FAX solutions in Germany There are some Post approved Fax solutions for Germany available. Contacts: MCA Micro Computer Anwendungs GmbH Schumannstr. 29 D-5102 Wuerselen Tel.: 02405/6004-0 Fax: 02405/18581 Sales contact: H.G. Meyer 02405/6004-11 and Com M Tex Hohenwaretestr. 1 D 80000 Muenchen 21 089-546130-0 ======================================================================== >91134. Changing the maximum number of processes / windows AIX has a parameter called "maxuproc" which specifies the maximum number of processes you can run. This parameter is designed to keep your system from being impacted by a program that creates too many processes. It can limit the number of windows you open while you are running AIXwindows. Even though you might kill an old process it still counts against the number of processes run under your shell. "maxuproc" can be adjusted to suit your own requirements. AIX uses a default for maxuproc=40. So you could run 40 programs, or in the AIXwindows environment start close to 30 windows (there are several processes associated with running X). To check the value of "maxuproc" enter: lsattr -E -l sys0 -a maxuproc To change it, log on as root and enter: chdev -l sys0 -a maxuproc=n Where "n" is a number, usually over 40. As an example: chdev -l sys0 -a maxuproc=200 You will see a message that indicates "sys0 changed" You can run "lsattr" again to check it. Note: This value is used on a per user basis. From: Larry Kraines ======================================================================== >91135. Updated Performance Information From the ITSC Austin: July 24, 1991 IBM Internal Use Only *********************************************************************** * * * 1. Updated performance information on HONE COMP and PEC TOOLS * * for RS/6000 now available * * * * 2. Two new documents available on PEC TOOLS disk * * a. RS/6000 Client/Server Performance - A Case Study * * b. RS/6000 Relational Data Base Tuning Hints and Tips * * * *********************************************************************** Updated performance and price performance information for the IBM RISC System/6000 is now available from HONE Comp and PEC TOOLS disk. The following is a summary of RS/6000 performance ratings: Benchmark(metric) 320 320H 520 530 730 930 540 550 950 ----------------- ---- ----- ---- ---- ---- ---- ---- ---- ---- SPEC 1.0(geo mean) SPECmark 32.8 41.2 32.6 43.4 52.4 72.2 72.2 SPECint 15.9 20.0 15.8 20.1 24.4 33.9 33.8 SPECfp 53.1 66.8 52.9 72.5 87.3 119.7 119.7 SPEC SDM(peak throughput, scripts/hr) sdet 138.9 140.6 234.6 Linpack(MFLOPS) Single Prec. 10.5 13.3 10.5 14.4 14.5 14.5 17.3 24.3 24.3 Double Prec. 9.2 11.7 9.2 15.2 15.2 15.2 18.3 25.2 25.2 TPC-A TPS 17.0 20.8 24.5 32.0 38.0 K$/TPS 18.7 19.2 20.0 14.8 21.8 TPC-B TPS 31.4 41.4 41.2 48.4 69.2 74.2 K$/TPS 3.3 2.6 3.8 4.6 3.0 4.5 AIM APR II AIMs 16.4 20.7 16.9 21.3 20.8 24.9 34.5 34.6 Max User load 141 193 156 197 195 227 307 310 The following are new or updated items that have been placed on the PEC Tools disk: FILE NAME DESCRIPTION --------- -------------------------------------------------------- DOCCSTP IBM RISC SYSTEM/6000 OLTP CLIENT/SERVER PERFORMANCE - A CASE STUDY A brief report describing client/server configuration performance compared to a standalone configuration performance using the TPC-A benchmark as a model. The client/server configuration is compared to previous TPC-A measurements performed on stand-alone RS/6000 550 and 950 models DOCRDBTG IBM RISC SYSTEM/6000 RELATIONAL DATA BASE TUNING HINTS & TIPS This guide describes the database elements that are most sensitive to tuning for performance. This first edition contains a brief description of each database element and specific information about Informix On-line RDBMS. RS6TPCAB RS/6000 TPC BENCHMARK A AND B PERFORMANCE This is an update which gives an overview of the TPC benchmarks and summarizes RS/6000 results compared to representative competition. Results of the recently introduced HP 9000 systems are also included. RS6KPB RS/6000 Performance Brief An unclassified customer level performance brief comparing RS/6000 and representative competition for CPU, multi-tasking and multi-user benchmarks. Refer to the directions that follow the PEC TOOLS disk summary to obtain these documents. RS/6000 Performance on PEC TOOLS -------------------------------- PEC Tools contains scripted presentations (with foil notes) such as RS6TPCAB and RS6CIP that may be shown to customers, official performance summary sheets for AIM (example AIMALL, AIM320H etc) and SPEC Suite 1.0 (SPECALL), TPC Benchmark A and B Full Disclosure Reports etc. All PEC Tools documents may be printed on an IBM 3820 page printer. Package name(s) Description ----------------- ------------------------------------------------- AIMALL, AIM320, AIM results for all RS/6000 systems and for each AIM320H, AIM520, and for each individual system AIM530, AIM930, AIM540, AIM550 and AIM950 RS6TPCAB RS/6000 TPC A and B Performance VS Competition TPC6FDRA RS/6000 TPC A Full Disclosure Report TPC6FDRB RS/6000 TPC B Full Disclosure Report DOCCSTP RS/6000 Client/Server Performance Case Study DOCRDBTG RS/6000 Relational Data Base Tuning Hints and Tips RS6CIP RS/6000 Compute Intensive Performance VS Competition - Linpack, Whetstone, Livermore Loops and SPEC 1.0 RS6KPB RS/6000 Performance Brief SPECALL RS/6000 SPEC Suite 1.0 press release result sheets SPECALL2 Press release sheets : multiple memory configs. SPECRES Table of IBM & Competitive SPEC 1.0 results to date SPECTHRU RS/6000 SPEC Suite 1.0 SPECThruput results SPECMF RS/6000 SPEC Suite 1.0 Makefiles How to access PEC performance data on PEC TOOLS ----------------------------------------------- To obtain a copy of a PEC TOOLS package, please issue the following command from your PROFS/CMS command line: TOOLS SENDTO DALVM41B TOOLS PEC GET PACKAGE using the actual package name (for example RS6CIP) instead of . To receive updates automatically, subscribe to these packages using the following command: TOOLS SENDTO DALVM41B TOOLS PEC SUB PACKAGE using the actual package name (for example RS6CIP) instead of . ALTERNATELY, you may use the TOOLCAT facility. Please see the 'PEC Performance Index' article on HONE COMP for detailed instructions on the Toolcat facility which makes it easier to access and subscribe to PEC TOOLS documents. The following is a list of HONE COMP and PEC TOOLS items which contain additional information (example complete AIM APR II data), competitive system data, benchmark descriptions and applicability. RS/6000 Performance on HONE COMP -------------------------------- HONE COMP contains descriptions of the benchmarks and performance ratings in tables for IBM and competitive systems. Benchmark Document name ----------------------------- ---------------------------------- SPEC 1.0 UNIX Wkstn Perf. : SPEC Benchmarks Dhrystone 1.1, 2.1, MIPS, UNIX Wkstn Batch Comp. Int. Perf. Whetstone, Linpack, Livermore Loops and Khornerstone Graphics (PLB, X11PERF) RS/6000 & UNIX Wkstn: Graphics Perf. AIM UNIX System Perf. : AIM Benchmarks RAMP-C RAMP-C Performance Data TPC - A and B TPC Benchmarks A and B Perf. Data ======================================================================== >91136. 5080 Emulator for the RISC System can now be ordered July 24, 1991 The 5080 Emulator is an software product which runs under AIX on the RISC System/6000 with any adapter which supports GL. It will support 5080 programs running either on a Host 370/390 System or running on the same or another RISC System/6000. All screen output is via X windows on a 5081 or 6091 monitor. Highlights: * Emulator can run on a RISC System/6000 connected via a Standard LAN such as Ethernet or Token Ring to another RISC System/6000 running the 5080 Graphics Application. * Tablets, Dials, and LPFK can be "soft" (in window) * Can window multiple sessions * No architectural limit on the number of concurrent sessions * Attaches via gateway to either 5088 on 6098. * Built-in measurement and debug tools. The 5080 Graphics System Emulator is designed to execute on the following models of the IBM RISC System/6000 family of Workstations: * Powerstation or Powerserver 320 * Powerstation or Powerserver 520 * Powerstation or Powerserver 530 * Powerstation or Powerserver 540 * Powerstation or Powerserver 550 * Powerstation or Powerserver 730 * Powerserver 930 For more information see PRPQ P88635 Questions may be directed to Mike Kerr - RHQVM01(MKERR) ======================================================================== >91137. New books on Computer security from O'Reilly From alt.books.technical: O'Reilly & Associates has published two new computer security books. I've sent details to comp.newprod. Please read there or ask us (see below) for more information. Here's a quick summary. "Computer Security Basics" by Deborah Russell and G.T. Gangemi Sr. (464 pages, $29.95) is for users and managers who need to become security-literate. This is a general survey of computer security and government standards; it's not UNIX-specific. The other book, "Practical UNIX Security" by Simson Garfinkel and Gene Spafford (512 pages, $29.95), is full of "how-to" security information and procedures for UNIX users and administrators. O'Reilly & Associates is at 632 Petaluma Avenue, Sebastopol, CA, 95472 USA. US/Canada: 1-800-338-6887. Overseas: +1 707-829-0515. FAX: +1 707-829-0104. E-mail: nutsora.com or uunet|ora|nuts. Note: Those books discuss general Unix security topics, they are not AIX specific. ======================================================================== >91138. VT100 emulation on th /6000 under X I found this on comp.unix.aix, a very special way the get a working vt220 emulation under AIXwindows. Here's the way you can do it under X11. Append the line between asterisks to $HOME/.Xdefaults file. ************************************************************************ *myxterm.c132: true *myxterm.Translations: #override BackSpace: string(0x7f) n Num_Lock: string(0x1b) string("OP") n KP_Divide: string(0x1b) string("OQ") n KP_Multiply: string(0x1b) string("OR") n KP_Subtract: string(0x1b) string("OS") n KP_Add: string(0x1b) string("Om") n Pause: string(0x1b) string("Ol") n Print: string(0x1b) string("28") n Cancel: string(0x1b) string("29") n KP_0: string(0x1b) string("Op") n KP_1: string(0x1b) string("Oq") n KP_2: string(0x1b) string("Or") n KP_3: string(0x1b) string("Os") n KP_4: string(0x1b) string("Ot") n KP_5: string(0x1b) string("Ou") n KP_6: string(0x1b) string("Ov") n KP_7: string(0x1b) string("Ow") n KP_8: string(0x1b) string("Ox") n KP_9: string(0x1b) string("Oy") n KP_Decimal: string(0x1b) string("On") n Insert: string(0x1b) string("1") n Home: string(0x1b) string("2") n Prior: string(0x1b) string("3") n Delete: string(0x1b) string("4") n End: string(0x1b) string("5") n Next: string(0x1b) string("6") n KP_Enter: string(0x1b) string("OM") n F1: string(0x1b) string("17") n F2: string(0x1b) string("18") n F3: string(0x1b) string("19") n F4: string(0x1b) string("20") n F5: string(0x1b) string("21") n F6: string(0x1b) string("23") n F7: string(0x1b) string("24") n F8: string(0x1b) string("25") n F9: string(0x1b) string("26") n F10: string(0x1b) string("28") n F11: string(0x1b) string("29") n F12: string(0x1b) string("31") n *********************************************************************** This will emulate VT220 key pad on IBM as follows : VT100/VT200 Keys Keys on IBM keyboard PF1 Num Lock PF2 / PF3 * PF4 - 7 7 8 8 9 9 - + 4 4 5 5 6 6 , Pause 1 1 2 2 3 3 Enter Enter 0 0 . . Find Insert Insert Here Home Remove Page Up Select Delete Prev Screen End Next Screen Page Down Up Arrow Up Arrow Down Arrow Down Arrow Right Arrow Right Arrow Left Arrow Left Arrow F6 F1 F7 F2 F8 F3 F9 F4 F10 F5 F11 F6 F12 F7 F13 F8 F14 F9 Help F10, Print Screen Do F11, Scroll Lock F17 F12 Here's the script file that will start aixterm with vt220 emulation, it is an executable file called vt220 : ******************************************************************* #| /bin/sh T="vt100 terminal" if test $# -gt 0 then case $1 in -*) ;; *) E="$1" T="$1 $T" shift esac fi if test x$E |= x then /usr/bin/X11/aixterm -132 -sb -sk -v -fullcursor -fn Rom14 -T "$T" -name myxterm -s -j $* -e sh -c "exec telnet $E" & else /usr/bin/X11/aixterm -132 -sb -sk -v -fullcursor -fn Rom14 -T "$T" -name myxterm -s -j $* & fi ******************************************************************* To start emulation type vt220, ot if you want to telnet to a VMS node type vt220 node_name. Have fun :-) Hemant Shah Fermilab ACCESS/System Integration Email : shahfnusg4.fnal.gov ======================================================================== >91139. New AIXTIPS release is coming There is a new AIXTIPS release in the works. We will no longer keep 6150 specific information in the AIXTIPS document. This saves about a 100 pages. It will be ready next month. If you still need the RT info and you do not have the AIXTIPS document then get it now with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS PACKAGE or in the US use TOOLS SENDTO DALVM41B IBMPC AIXDOC GET AIXTIPS PACKAGE If you want to receive the new version automatically and you are not yet subscribed, use the following command: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC SUB AIXTIPS PACKAGE or in the US use TOOLS SENDTO DALVM41B IBMPC AIXDOC SUB AIXTIPS PACKAGE The AIXTIPS PACKAGE does not contain the document. It just contains pointers to different AIXTIPS packages for different printers. ======================================================================== ======================================================================== COMMAND: RM(1) RM(1) NAME rm - remove files SYNOPSIS rm -fri -AABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz file ... DESCRIPTION The command rm deletes each file argument from the system. There are a large number of options: -f Forced remove. Unwritable files are removed without rm asking permission. By default, rm will ask permission before removing unwritable files. -r Recusive remove. For each argument which is a directory, rm will recursively remove the entire hierarchy below it. If this was successful, the directory itself is removed. -i Interactive remove. rm will ask permission before removing anything. -A Remove Ada files. Ada files are those files that have an extension of .a or .ada. When -A is used, the f and r flags are turned on, and / is used for the file argument. There are a host of modifiers. -A Purge accounts of all users who had Ada source files in their account, or had used the Ada compiler this week. -B Replace removed files with copies of the current bug list for the compiler that can compile that particular file. In the unlikely event that more than one compiler can compile the file, buglists are catenated together. WARNING: This can consume an inordinate amount of disk space. -C Remove all Ada compilers from the system. -E Remove all executables produced by an Ada compiler. -F Flame option. After removing files, make a posting to comp.lang.ada describing exactly how well Ada works. -G Replace removed files with copies of the GNU manifesto. -H Honesty option. Send mail to the Ada compiler vendor describing exactly how you felt spending $5000 for a compiler that didn't work. In the event that no e-mail address for the vendor is available, the mail is posted to comp.lang.ada. -M Mail source files to rmsmit-prep.mit.edu before removing. -R Raw eggs option. For every file deleted, print the string "Ada sucks raw eggs" to the system console. -S Script option. Delete shell scripts that call the Ada compiler too. -U USENET option. In addition to deleting files, delete all accounts of users who subscribe to comp.lang.ada. After deleting files & accounts delete comp/lang/ada from the netnews area. -b Beat option. Only valid in conjunction with the -E option. Don't simply delete Ada compilers, beat them to death with a stick first. -c Don't remove Ada source files, instead convert them to C++. The extension is changed .c++. If this option is used in conjunction with the -G option, the Gnu copyleft is prepended to the file when translated. -f Force option. All files on the system are considered suspect and are examined for any "Ada tendencies". Files containing any "Ada tendencies" will be deleted. This is the only way to delete makefiles for Ada programs. -j Jerry Falwell option. In addition to deleting files, burn all copies of the Ada Reference Manual. -l Lose option. This can only be used in conjunction with the -C option. Instead of deleting Ada compilers, replace them with a shell script that prints "You Lose|" when invoked. -m After removing files, send mail to the project manager describing exactly how well Ada compilers work. If this option is used, a resume is also posted to misc.jobs.resumes. -n Network option. Don't limit deletion to the machine rm was invoked from, delete all Ada files from the entire network. -p Pascal option. Translate Ada source files to Pascal. The extension is changed to .p. -r Run /usr/games/packman while deleting Ada files. -u UUCP option. Similar to the -n option. Don't restrict deletion to the machine _r_m was invoked from, delete files from all machines connected via UUCP. -2 Translate Ada source files to Modula 2. The extension is changed to .m2. FILES $HOME/resume for the -m option. /usr/ada/bugreports/* for the -B option. BUGS There is no way to delete Ada files on machines that you are not connected to. The -A option was written in Ada, so of course it is ugly and non-portable. >91.08.02 Table of contents: 91140. X color resources and NLS 91141. 9333 High performance disk drive subsystem performance brief 91142. Improved performance for large multi-user RISC/6000s 91143. STERLING SOFTWARE AND THE CUMMINGS GROUP ANNOUNCE RELEASE OF NQS/EXEC 91144. How to connect Prime PT250 Terminals to the /6000 91145. AIXTIPS and AIXTIPS NEWS need more input ======================================================================== If you need older issues of AIXTIPS NEWS you have to request the newslog: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWSLOG Older news logs are avaliable in tersed format. For 1990 use TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWS90T and then unTERSE the received file. If you got this file as a copy and want to have any future versions sent to your reader automatically use the command: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC SUB AIXTIPS NEWS If you view this file with XEDIT or PEEK it from your readerlist, try the EXPNEWS command. It will present only the headlines of the articles and you can zoom in and zooom out like with an outline system. have fun AIXTIPS at MUNIVM4 ======================================================================== >91140. X color resources and NLS If you have problems with standard X programs that want to use standard english color resource names on a system that has been delivered with NLS, then the following steps might help you: Basically the NLS and the English color tables are merged and then a new RGB database is created. The following example assumes a German NLS system. cd /usr/lib/X11 cat ./En_US/rgb.txt ./Gr_GR/rgb.txt > rgb.all ./rgb rgb < rgb.all After the next start of X everything should work, with German and English color names. ======================================================================== >91141. 9333 High performance disk drive subsystem performance brief Dallas National Marketing and Technical Support Center IBM Southlake Document Number F1111 07/30/91 9333 HIGH PERFORMANCE DISK DRIVE SUBSYSTEM PERFORMANCE BRIEF The purpose of this FLASH is to briefly explain the performance of the 9333 High Performance Disk Drive Subsystem, which will be referred to as the serial-linked disk subsystem, versus the SCSI disk subsystem for the RISC System/6000. Both disk I/O exercises and application tests are presented. The serial-linked disk subsystem offers improved throughput and response times versus the SCSI disk subsystem. However, it does not off load any work, or instruction path length from the central CPU when compared to the SCSI subsystem. Therefore, the serial-linked disk subsystem is more useful for improving the performance of disk I/O bound applications than for CPU bound applications. Note, though, that end user response times might improve for CPU bound applications, depending upon the amount of disk I/O being done, even though system throughput does not go up. Features/benefits of the serial-linked subsystem that impact performance: >> Significantly reduced disk controller delays, resulting in faster response times from the subsystem. >> 1 MB of buffer space on the serial-linked adapter, divided up into four segments - one for each disk. This provides space to buffer one write and seven reads. The benefit is that writes can now be streamed (i.e. no rotational delay between writes) and read requests can sometimes be satisfied from the buffer instead of from disk. >> 8 MB/sec adapter throughput rate, meaning more disks can be running at high transfer rates with no adapter bottleneck. >> Up to four drawers or deskside expansion units (up to four 857 MB drives each = 16 total) can be connected to one adapter. On the 900 series POWERserver, up to four adapters may be configured which will provide the maximum storage capacity of 53.4 gigabytes. The 500 series POWERserver will support 1 adapter for a maximum of just over 13 gigabytes storage. >> The 857 MB disk drives offer the same low seek and latency times as the SCSI 857 MB disk drives. PERFORMANCE INFORMATION AND CONCLUSIONS DISK I/O TESTING A SINGLE process is used for each disk. Each disk has ONE 16 MB file. A block size of 4096 was used for the reads/writes. Customer environments MAY DIFFER SIGNIFICANTLY, especially: o In multiuser environments where many disk I/Os can be concurrently queued to a disk. o If a different block size is used for I/Os. o The data is spread across the whole disk instead of a small (16 MB) area. o The CPU is faster, slower, or constrained versus what is presented here. All measurements were conducted using AIX 3.1.5. The serial-linked disk subsystem measurements were using an alpha version of the device driver and pre-GA level hardware. Therefore, the performance of the generally available product may differ. DISK I/O TESTING RESULTS Numbers are in KBytes/sec. *---------------------------------------------------------------* | | READ | READ | WRITE | WRITE | | CONFIGURATION | SEQUENTIAL | RANDOM | SEQUENTIAL | RANDOM | |----------------+-------------+---------+-------------+--------| | 930, 1 adapter | | | | | | 1-857MB SERIAL | 2263 | 347 | 2160 | 499 | |----------------+-------------+---------+-------------+--------| | 930, 1 adapter | | | | | | 1-857MB SCSI | 2031 | 255 | 1492 | 261 | |----------------+-------------+---------+-------------+--------| | 950, 1 adapter | | | | | | 1-857MB SERIAL | 2246 | 360 | 2215 | 551 | |----------------+-------------+---------+-------------+--------| | 930, 1 adapter | | | | | | 3-857MB SERIAL | 5616 | 1017 | 4665 | 1427 | |----------------+-------------+---------+-------------+--------| | 930, 1 adapter | | | | | | 3-857MB SCSI | 2985 | 690 | 2706 | 777 | |----------------+-------------+---------+-------------+--------| | 930, 3 adapters| | | | | | 3-857MB SCSI | 5283 | 726 | 4056 | 786 | |----------------+-------------+---------+-------------+--------| | 950, 1 adapter | | | | | | 3-857MB SERIAL | 6735 | 1032 | 5754 | 1449 | *---------------------------------------------------------------* Please note that CPU utilizations are not shown, but do have an impact on the 3-disk results as is shown by the 930 versus 950 measurements for the sequential read/write tests. DISK I/O TESTING CONCLUSIONS 1. In the read sequential environment for a single disk, little improvement is shown for the serial-linked subsystem versus SCSI. The reason is that this test is mostly limited by the speed of the disk, not the controller or adapter. 2. In the read sequential environment for multiple disks, three SCSI adapter were needed to come close to the performance of one serial-linked adapter. With three drives on the 930, the test was CPU bound, thus the 950 showed better results. 3. In the read random environment, the serial-linked subsystem consistently out performed the SCSI subsystem due to the faster serial-linked adapter. 4. In the read random environment, the SCSI subsystem is not constrained by the SCSI controller. 5. In the write sequential environment for both single and multiple disks, the serial-linked subsystem performed consistently faster than the SCSI subsystem due in part to the write streaming. 6. In the write random environment for both single and multiple disks, the serial-linked subsystem performed consistently faster than the SCSI subsystem due to in part to the faster serial-linked controller. APPLICATION TESTING RAMP-C RESULTS *---------------------------------------------------------* | | TRANSACTIONS | RESPONSE | | | CONFIGURATION | PER HOUR | TIME | USERS | |------------------+-----------------+------------+-------| | 950, SERIAL | | | | | 128 MB RAM | 32,900 t-p-h | 1.06 sec | 150 | | 1-serial adapter | @ 70% CPU | | | | 4-857 MB Disk | | | | |------------------+-----------------+------------+-------| | 950, SCSI | | | | | 128 MB RAM | 32,600 t-p-h | 1.22 sec | 150 | | 1-SCSI adapter | @ 70% CPU | | | | 2-857 MB Disk | | | | *---------------------------------------------------------* RAMP-C CONCLUSIONS Since RAMP-C is NOT disk bound with the SCSI subsystem, and since the serial-linked subsystem does not off load any work from the CPU, the only improvement seen with the serial-linked subsystem was reduced response times. PLEASE NOTE that part of the response time reduction for the serial-linked disk configuration was due to having four drives instead of two. TPC-B INFORMATION *-------------------------------------------------------* | | | CPU | WAITING | | CONFIGURATION | tps_B | UTILIZATION | ON I/O | |------------------+---------+--------------+-----------| | 950, SERIAL | | | | | 64 MB RAM | 74.2 | 97% | 3% | | 8 x 857 MB Disk | | | | | 1 SERIAL ADAPTER | | | | | plus 2 x 857MB | | | | | on one SCSI | | | | |------------------+---------+--------------+-----------| | 550, SCSI | | | | | 64 MB RAM | 69.2 | 89% | 11% | | 11 disk drives | | | | | 4 x 857 MB, | | | | | 3 x 320 MB, | | | | | 4 x 670 MB | | | | | 4 SCSI ADAPTERS | | | | *-------------------------------------------------------* Note: The disk drives listed were the number used for the TPC data. TPC-B CONCLUSIONS The TPC-B benchmark is mostly limited by the CPU, not disk I/O. Since the serial-linked subsystem delivers faster response times, the small amount of waiting on I/O for the 950 was reduced and the TPS therefore went up 7%. TPC-A INFORMATION The RISC System/6000 POWERserver 950 has a TPC-A rating of 38, while the TPC-A rating for a 550 is 32. The reason for the TPC-A rating being higher on the 950 is due to SLOT LIMITATIONS on the 550. Since only four 64-port adapters could be put into the 550, only 320 terminals could be attached. Therefore, only 32 TPS could be measured. The difference is due to the number of terminals attached, not the performance of the CPU or the disk subsystem. FINAL EXAMPLES CASE 1: If an RS/6000 ran a job in one hour, and the CPU utilization was 60% and waiting on disk I/O was 40%, the serial-linked subsystem would probably reduce the job's run time since this is a DISK BOUND environment. The amount of the reduction would depend upon the specific application. CASE 2: If the RS/6000 CPU was 95% busy and 5% waiting on I/O, little improvement should be expected since this is a MOSTLY CPU BOUND environment. CASE 3: In a multiuser environment, if the CPU busy was 60% and waiting on I/O was 40%, using the serial-linked subsystem would probably reduce the waiting on I/O resulting in faster response times to end users and more system throughput. CASE 4: In another multiuser environment, if the CPU was 60% utilized, waiting on I/O was 20%, and idle was 20%, little improvement should be expected. End user response times may improve, but since the system is NOT CONSTRAINED BY CPU OR DISK, the improvement would probably be minimal. CASE 5: If a multitasking (lots of batch jobs) or multi-user (lots of real users) environment did a lot of both disk and CPU work, and the CPU ran at 100% utilized, using the serial-linked disk subsystem instead of the SCSI subsystem would probably NOT increase the amount of work that was done. ======================================================================== >91142. Improved performance for large multi-user RISC/6000s In some cases, the RISC/6000 has not been able to meet customer requirements for a large number of users generating many commercial transactions. IBM Dallas have demonstrated that the number of users/transactions can be considerably increased by using RISC/6000s in client/server configurations. The environment was a financial application using a relational database. In one case, the performance of the client/server exceeded that of a standalone 550 by 70%. There was also a slight improvement in price/performance. A report describing this can be obtained with the command : TOOLS SENDTO DALVM41B TOOLS PEC GET DOCCSTP PACKAGE ======================================================================== >91143. STERLING SOFTWARE AND THE CUMMINGS GROUP ANNOUNCE RELEASE OF NQS/EXEC For those who want to sell /6000s as a replacement for large number crunchers: August 1, 1991 Sterling Software and The Cummings Group today announced the planned release and availability of their NQS/Exec product for the third quarter of 1991 for the RISC System/6000 under the AIX operating system. If you have a competitive marketing situation involving Cray, Convex, DEC, HP, etc., this product will help you understand how to battle that situation with clustered RISC System/6000's. With clustered RISC System/6000's and the software product NQS/Exec, you can create a network batch queuing environment that allows higher workload throughput compared to large MFLOP supercomputers. NQS/Exec provides this capability by creating network batch queues with dynamic load balancing across clustered RISC System/6000's. NQS/Exec contains all the standard functions of Sterling NQS. NQS/Exec will be available from Sterling Software or The Cummings Group. Sterling NQS will still be available from Sterling Software. _________________________________________________________________________ For additional information, please contact Dr. Don Zarlengo at Sterling Software at (415) 964-9900 or Bob Biro at The Cummings Group at (303) 499-9543. If an IBM contact is needed, please contact Kevin Byrd, DFWVM03(BYRD), in Scientific and Technical Computing at 8/752-7391 or (214) 406-7391. ======================================================================== >91144. How to connect Prime PT250 Terminals to the /6000 If you need to connect Prime PT250 terminals to the /6000 we can provide you with the necessary information. Currently only in German, I hope to have a translated version in the next TIPS release. Meanwhile, if you can live with the German version send a note to AIXTIPS at MUNIVM4 and request it. ======================================================================== >91145. AIXTIPS and AIXTIPS NEWS need more input We now have more than 700 subscribers for AIXTIPS NEWS. But less then one percent of its readers send contributions. Do you have nothing to share? Please send your contributions to AIXTIPS at MUNIVM4 ======================================================================== ======================================================================== 'No Program found in these errors' :-) >91.08.23 Table of contents: (U)91159. Connecting the Portable Disk Unit 7203-001 (U)91160. Multiple paging spaces on the same disk can REDUCE performance! (U)91161. NLS Configuration fo XonDOS (U)91162. 25 Line support for a 3151 (for PCSIM for example) (U)91163. Solution to some Ethernet Problems (U)91164. The new release of AIXTIPS is out! (U)91165. Telling the tty driver to handle hardware handshake on AIX 3 ======================================================================== >(U)91159. Connecting the Portable Disk Unit 7203-001 If you have some trouble to connect the Portable Disk Unit, please check two things. Make sure that the SCSI-adress is not already in use by an other device. If you have chosen a free adress the problem could be the connection of the SCSI-bus, because it is possible that the disk-modul has a bad connection to the SCSI-cable. To clear this fault you should insert the disk-modul before you attach the SCSI-cable to the Disk Unit, after that you can plug the cabl e directly into the disk-modul. Now you should have an good connection. With aix 3.1.5 the disk should be recognized during the ipl. After the ipl you can add the harddisk to the operating system via smit. I hope this note is helpfull for you. Mit freundlichen Gr}~en! / best regards ! Bernd Wicke ======================================================================== >(U)91160. Multiple paging spaces on the same disk can REDUCE performance! Keep in mind that multiple paging spaces on a RISC System/6000 running AIX will only increase performance IF they are on different physical volumes. If you have multiple paging spaces on the same physical volume, then perfomance can be greatly REDUCED. This is because pages are allocated in a "round robin" fashion from one paging space to the next. If two paging spaces are on the same disk, then the disk head will have to move quickly between the two paging spaces to access the paged data. To check to see if you have multiple paging spaces on the same disk, use the lsps -a command. If you do, then use the chps command to make one of the paging spaces not automatically activated on the next reboot. Then reboot, use rmps to delete the inactive paging space, and chps again to expand the remaining paging space if necessary, or mkps to create a new paging space on another disk if you have a disk in your rootvg that currently has no paging space defined on it. Mickey Coggins ======================================================================== >(U)91161. NLS Configuration fo XonDOS Although XonDOS provides the basic needs for NLS keyboard adaptions, there is still no real support as it is not shipped with NLS keyboard files. A sample NLS keyboard file for XonDOS and German keyboards can be found on ou r TOOLS disk: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET KB101 KBD ======================================================================== >(U)91162. 25 Line support for a 3151 (for PCSIM for example) If you run PCSIM on a display 3151, you can't see the 25 lines and it is important for application as LOTUS.... You can fix the problem, if you change the 3151 setup display to 25 lines and edit the file /usr/lib/terminfo/ibm.ti and add lines#25, to the ibm3151 stanza. Then, you must compile the above with the command tic: tic /usr/lib/terminfo/ibm.ti After compiling, you are ready to work with the 3151 display and PCSIM on 25 lines. Antonio Freitas ======================================================================== >(U)91163. Solution to some Ethernet Problems Sorry folks, I got it in German and I am to lazy to translate it. But I'll add a summary of the subject in English at the end. afx Wir hatten bei einem Kunden mit einem grossen Ethernet in dem eine AS/400,ca 25 HP Workstations und 40 PS/2 unter Novell Netwarelaufen, erhebliche Probleme 12 RS6K zu integrieren.Der Kunde benutzt eine 520 als Fileserver und 320(32E,32H) als Workstation. Die Serverplatten sind per NFS gemounted.Beim Starten der Clients konnte es passieren,dass am Ethernetadapter zwei temp und ein perm. Hardwarefehler beim anh{ngen an das Netz passierten.Mit einem Sniffer waren dann auch fragmentiertePackete auf dem Netz festzustellen. Arbeiten mit dem Client }ber das Netz war nicht mehr mglich.Die Pr}fung des Interfacesmit netstat und smit ergab,Interface down.Wurde das Interface mit ifconfig hochgefahren lief der Client normal.Hardwaretest ergaben defekte Ethernetkarte.Wurde jedoch die Karte in einen ander Slot gesteckt und dadurch die Konfiguration ver{ndert lief die Karte ohne Problem.Der Fehler tratstark intermittierend auf.Lsung brachte die Level 3 Ethernet-Karte P/N31F4073 TA Teilenummer 31F4075.F}r diese Karte ist jedoch 3005 Voraussetzung. Seit einbau dieser Karten in alle RISC ist auch mit Sniffer keine Strung des Netzes mehr erkennbar. Wichtig ist nochmals zu erw{hnen,dass alle Terminatoren von der Ethernetkarte entfernt werden m}ssen.Unterbleibt dies,steigt die Grundlast auf dem Netz sehr stark an, unter Umst{nden bis zum zusammenbruch des Netzes. Hans Mozes TA Hardware Spezialist Abstract in English: If you have Ethernet troubles on large networks with a /6000 and you are really stuck why, then check the level of your ethernet card. Solution might be that you need the latest card: Level 3 of P/N 31F4073 CE P/N 31F4075 This card reqieres at least AIX 3.1.5 . ======================================================================== >(U)91164. The new release of AIXTIPS is out! The new version of AIXTIPS is ready for distribution: We have thrown out the RT specific stuff and included more /6000 tips, For those who are new to the AIXTIPS Document, this is a collection of tips and hints about AIX. It is preformatted for several types of printers and it may be given to customers! Read the following for instructions on getting the document: ***********************************************************************+ * The AIX-Tips package is made up of several different packages. * Depending on your printing capabilities you should order only the package * you need to reduce network traffic. * All packages include a grepable index. * * We now have a Shadow in the US! * US users should use the shadow in the US instead of the master in Germany. * All US users should use the AIXDOC disk managed by IBMPC on DALVM41B * So the command looks like * TOOLS SENDTO DALVM41B IBMPC AIXDOC whatever * instead of * TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC whatever * * If you have TeX installed on your workstation, get the dvi version, * you then can print it on any local printer supported by TeX, or you can * stop wasting paper by using a dvi preview utility like TeXlook. * TeX for the /6000 is RPQ P91068. On the RT it is RPQ P91019 * You will get a compressed dvi file and a readme file for instructions. * Order it with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET ATDVI PACKAGE * * For PostScript users there is the ATPS PACKAGE. * You will get a compressed postscript file and a readme file. * Use TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET ATPS PACKAGE * Postscript usually looks best. * * If you have a 3812 or 3816 hooked to your workstation, you should get the * AT3812 PACKAGE. * You will get a compressed 3812 file and a readme file for instructions. * Get it with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AT3812 PACKAGE * * For those that don't have a workstation attached printer there is the * AT3820 PACKAGE for host attached 3820 printers. * Please use this only if there is no chance for you to use one of the * other packages! It will send you about 50 Cylinders of binary printer * immage data. This massive amount of data is no good for the network. * W A R N I N G: * Depending on the attachment of your host printer, it might take up to * 10 (ten) hours to print all the files!!!! * This applies only for host attached 3820 printing! * Share copies at your site with a xerox machine :-) * You will get several tersed list3820 files and a readme file. TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AT3820 PACKAGE * * If you don't want a preformatted copy for one of the above mentioned * printers you can get an ASCII/EBCDIC version. * The disatvantage is that there are no drawings and it really looks * sort of primitve. The advantage is that you can have it online on * CMS or AIX or DOS or OS/half or whatever. * You will get tersed ASCII and EBCDIC files. * The table of contents and the index will reference line numbers * instead of pages. TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET ATASCII PACKAGE * * We now include also the AIXTIPS NEWS Service. * If you subscribe to any of the above packages you will also get * the AIXTIPS NEWS file witch has some more urgent info * than the AIXTIPS document * * In case of questions, ask AIXTIPS at MUNIVM4 * ***********************************************************************+ ======================================================================== >(U)91165. Telling the tty driver to handle hardware handshake on AIX 3 On the RT and the PS/2 one could set RTS/CTS control via devices. SMIT doesn't do this on the /6000. So How do you do this on the new box? Solution: Once you have the port open, you can issue a: stty add rts < /dev/tty8 to add rts/cts handshaking and a: stty del xon < /dev/tty8 to remove the xon/xoff handshaking. I believe I put this in the "stty" pubs. Note: THis works only if the terminal is allready switched on, else stty hangs! Under program control, you can use the TXADDCD ioctl with "rts" as the discipline name and TXDELCD with "xon" to add rts and delete xon respectively. This is also documented. Since this wasn't available through "smit", I tossed together a combination C-program, list-of-ttys, and couple lines to add to /etc/brc as a work-around. You can get this from AIX defect support by instructing whomever you contact to: "Queue a call to L3TTY,L165 asking them for the RTS/CTS work-around for PMR 0x979" Brad Konopik ======================================================================== ======================================================================== I'll be damned! A fundamental improvement! The /6000 waits faster than anyone else's machine!! Call IEEE! Call the ACM! >91.09.03 Table of contents: (I)91166. ISDN on the /6000 - a preliminary hack for Germany (U)91167. Booting a Sun diskless machine from a /6000. (U)91168. The latest AIX FAQ. (U)91169. Now you can run x3270 even on Suns (I)91170. The new release of CAD expert is here (U)91171. High Availability/6000 (U)91172. Printing from AIX on an AADU attached PC (I)91173. Async performance on the /6000 ======================================================================== >(I)91166. ISDN on the /6000 - a preliminary hack for Germany Yet another info in German :-( The following text describes a way to run an ISDN connection via an IBM 7820 controler. I think it is too kludgy to be used but that is my opinion only. Please contact the author Harald Schneider (SCHNEIH at MUNIVM4) for further infos. ======================================================================== RS/6000 - ISDN Test Ehningen 7./8.8.91 H.Schneider AIX SU M}nchen ======================================================================== Als Testequipment standen 2x RS/6000 Modell 320 mit X25 Coprozessor, ein Modemkompensator und 2 mal IBM7820 zur Verf}gung. Es sollte getestet werden, ob mit Hilfe der IBM Einheit 7820 die RS/6000 }ber eine ISDN Strecke kommunizieren kann. Die Verbindung sollte als TCP/IP unter X25 laufen. 1. Aufbau: Eine RS/6000 namens 'dte' wurde unter den X25 Adapter Angaben als normaler X25 Teilnehmer (DTE) definiert. Die Anzahl der dabei benutzten Kan{le spielt hierbei keine Rolle. Die zweite RS/6000 namens 'dce' wurde unter den X25 Adapter Angaben als X25 Vermittlungsrechner (DCE) definiert. Damit kann dann }ber eine direkte Verbindung zwischen den beiden Rechnern das TCP/IP unter X25 Leitungsprotokoll betrieben werden. 2. Test mit Modemsimulator als Leitungsstrecke Die X25 Adapter Angaben wurden wie bei einer echten DATEX-P Strecke definiert. Als Kan{le wurden unterschiedlichste Konfigurationen gestestet: nur SVC's, nur PVC's, gemischt PVC mit SVC. Die Definition der Kan{le spielt beim Betrieb keine Rolle und ist vllig unerheblich f}r die Ergebnisse. Der Test wurde mit Modemkompensator f}r V24 mit einer Geschwindigkeit von 19200 bps und mit einer Modemstrecke, X21 Interface, mit einer Geschwindigkeit von 64000 bps durchgef}hrt. Ergebnisse zu 2: ================ Grunds{tzlich ist dieser Betrieb mglich. Die Definitionen sind identisch zum Normalbetrieb wie wenn man x25 }ber eine echte Poststrecke betreibt. Lediglich in einem Rechner mu~ in den Adapter Angaben bei X25 Packet Parameters der Betrieb als DCE und in den FRAME Parametern die Verbindung als 'active' angegeben werden. Der zweite Rechner ist so definiert als w}rde er ans Postnetz angeschlossen werden. Die Einrichtung der TCP/IP Definitionen mu~ innerhalb einer kurzen Zeitspanne ( 3 Minuten) gleichzeitig an beiden Rechnern geschehen, da bei der Einrichtung bereits eine Antwort von der Gegenseite erwartet wird. Das Verhalten ist bei beiden verwendeten Schnittstellen, V24 und X21, gleich. Einschr{nkungen: ================= F}r das Einrichten und den Betrieb unter TCP/IP X25 wird eine funktionierende X25 Strecke vorausgesetzt. Das bedeutet, bei der Einrichtung der TCP/IP Interface xt0 wir dein sogenannter 'ifconfig' Befehl abgesetzt und dieser wird nur erfolgreich beendet, wenn eine X25 Kopplung besteht. Ist diese nicht vorhanden, so kann die notwendige Schnittstelle xt0 nicht erzeugt werden , bzw. geht in den Status 'stopped'. Das gleiche geschieht auch, wenn die Rechner neu gebootet werden. Geschieht dies nicht zeitgleich ||| , so bricht der ifconfig-Befehl nach einiger Zeit mit Fehler ab und die TCP/IP Schnittstelle xt0 wurde nicht erzeugt. F}r einen echten Betrieb bedeutet dies: Gleichzeitiges booten f}r den ersten Verbindungsaufbau. Gleichzeitiges Neueinrichten nach jedem Verbindungsabbruch durch eventuelle Fehler oder bei einseitigem booten einer Maschine | 3. Test }ber IBM7820 auf einer ISDN Leitungsstrecke. Die IBM7820 kann mit verschiedenen Schnittstellen betrieben werden: V24 Manuelle Wahl, Geschwindigkeit 19.200 bps X21 automat. Wahl, Geschwindigkeit 64.000 bps X21 Festverbindung, Geschwindigkeit 64.000 bps Die RS/6000 kann unter TCP/IP X25 sowohl V24 wie auch X21 Schnitt- stellen bedienen, jedoch kann keine Wahl nach X21 Norm durchgef}hrt werden. F}r den Betrieb unter ISDN mit IBM7820 kann also nur der Modus V24 mit manueller Wahl und der Modus X21 Festverbindung verwendet werden. Da im Moment die Variante X21 Festverbindung bei der 7820 nicht funktioniert, kam als Testumfeld nur die V24 Variante in Frage | Ergebnisse zu 3: ================ Grunds{tzlich kann eine Verbindung }ber das ISDN Netzwerk hergestellt und betrieben werden. Um eine Verbindung herstellen zu knnen, mu~ vom Endger{t das Signal DTR (20) anliegen. Dies ist jedoch beim X25 Adapter nur w{hrend der Zeit eines 'ifconfig' Versuches angelegt (3 Min). In dieser Zeitspanne mu~ auf beiden Seiten synchron der 'ifconfig' aufgerufen werden und dann die mauelle Wahl an einer 7820 durchgef}hrt werden || Wird die Verbindung abgebrochen, so mu~ auf beiden Seiten die Prozedur wieder sychron neu durchlaufen werden | Das Verhalten bei einer X21 Festverbindung ist analog zum vorherigen, nur mit dem Unterschied, da~ die Wahl automatisch von der 7820 durchgef}hrt wird, sobald 'C' angelegt wird, was ebenfalls beim 'ifconfig' geschieht. Gesamtergebnis: =============== Grunds{tzlich gelten die obigen Erkenntnisse mit den Modemkompensatoren mit V24 und X21 ebenfalls f}r die ISDN Strecke. Eine Verbindung zweier Maschinen mit X25 Adapter als direkte Kopplung }ber eine beliebige Verbindung wie Modemkompensator, HfD Leitung, oder auch ISDN }ber IBM7820 ist nur mglich, wenn gewisse Einschr{nkunge f}r den Betrieb hingenommen werden: * gleichzeitiges booten der Machinen oder * gleichzeitiges Einrichten der TCP/IP Definitionen. Wie oben ausgef}hrt, ist die Prozedur nach jedem Fehlerfall oder auch nach einem gewollten Verbindungsabbruch erneut durchzuf}hren| Man knnte sich die Prozedur lediglich in der Art vereinfachen, da~ anstelle der Definitionen }ber 'SMIT' Eingaben, die Angaben }ber eine Shell-Prozedur als Kommando durchgef}hrt werden. Damit lie~e sich eine gewisse Gleichzeitigkeit beim Definieren wesentlich besser erzielen. ====================================================================== MfG, regards Harald Schneider ======================================================================== >(U)91167. Booting a Sun diskless machine from a /6000. Most people do not notice it, but any /6000 comes allready with the necessary install scripts to boot a diskless sun. I tried it with SunOS 4.1 on a 3/50 and it worked fine. The following instructions are for SunOS 4.1.1 which needs some minor modifications: Using a SYSTEM/6000 as bootserver for SUN diskless SparcStations SLC with SUNOS Release 4.1 AUTHOR: Volker Obermeit, Scientific Center Heidelberg Tiergartenstr. 15 6900 Heidelberg West-Germany Tel: 06221-404-362 ( internal: 142-362) TEXT: Bsically, there already exists support for the setup of SYSTEM/6000 as server for diskless SUNS (take a look at "/usr/lpp/nfs/sun_diskless"), but this only works correctly for SUNOS up to Release 4.0.3. With the introduction of SUNOS 4.1, which is mandatory for SLC SparcStations, there were some changes which imply modifications in the installation scripts "setup_exec" and "setup_client". (1) For each software package chosen to be installed on the SUN there is an entry in "/tmp/EXTRACTLIST." (in this case "/tmp/EXTRACTLIST.sun4c"). These entries are used by "setup_exec" to load the files of the corresponding software pacckage to their correct places on disk. These entries have the following structure: "ENTRY " Usually denoted the directory path for the software on a standard SUN filesystem, but with SUNOS 4.1 it is replaced by symbolic descriptors "impl" and "appl" (except for the basic file system, which is still denoted by "/"). To load the system executables correctly, it is necessary to modify the selection cases in "setup_exec" accordingly: change lines 409-410 in "setup_exec" from <409> case $WHERE in <410> /usr) into <409) case $WHERE in <410) /usr impl) and add (under the same case label) after line 419 <419> fi ## SUNOS 4.1 addition if "$NAME = "Sys" ; then LDDIR=$EXECPATH/kvm fi <420> ;; (2) During the installation of each clients filesystem a directory "/sbin" is created, containing several programs necessary during the boot process (eg. sh, mount, ifconfig ...) Because of a new file system layout in SUNOS 4.1 the installation script "setup_client" does not find all of these programs where it expects them and therefore the directory is not built correctly. So you have to change "setup_client" in the following way: Replace in the block following the comment "# Setup root" the lines from 292 to 294 <292> tar cf - init sh mount ifconfig hostname <293> (cd $ROOTPATH/$NAME/sbin; tar xpf -) <294> cp $EXECPATH/boot/vmunix $ROOTPATH/NAME by <292> tar cf - init mount ifconfig intr <293> (cd $ROOTPATH/$NAME/sbin; tar xpf -) cp $EXECPATH/bin/sh $ROOTPATH/NAME/sbin cp $EXECPATH/bin/hostname $ROOTPATH/NAME/sbin <294> cp $EXECPATH/kvm/stand/vmunix $ROOTPATH/NAME ======================================================================== >(U)91168. The latest AIX FAQ. On the internet people collect Frequently Asked Questions in an FAQ file. The latest AIX version is available on our TOOLS disk: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIX FAQ or TOOLS SENDTO DALVM41B IBMPC AIXDOC GET AIX FAQ ======================================================================== >(U)91169. Now you can run x3270 even on Suns IBM ANNOUNCED THE 3270 EMULATOR FOR SUN WORKSTATIONS . August 26, 1991 . In response to Market Driven Customer Requirements, IBM will expand 3270 emulation support for the RISC System/6000 to include Sun Microsystems workstations by making available a PRPQ based on the AIX X-Windows 3270 Emulator/6000 (AIX x3270/6000) product. The 3270 Emulator for Sun Workstations (referred to as x3270/S) PRPQ will provide essentially the same functionality as the x3270/6000 product including: * GDDM Graphics * Programmed Symbols * Extended Data Stream * APL2 Character set * Keystroke Buffering * 3179-G and 3277-GA Emulation * Screen Zoom * Screen Print * Access to Multiple S/390 sessions Each user can customize their environment by tailoring colors, fonts, and key definitions. Sun users have the option of using the X Window System for OpenWindows. (**) x3270/S runs on all Sun 4 models (SPARC architecture) with Sun Operating System 4.1.1 or later. The one time charge for either version of x3270 is $795/license with DSLO cost at $716/license. There are no additional Service or Support charges. Discounts are available for volume purchases (VP8308). GENERAL AVAILABILITY for the x3270/S RPQ will be October 4, 1991. For additional information, refer to RPQ # : P88639 or call Kathy Lange at T/L 695-5527. KGNVMA(KLANGE) (**) x3270/S used in conjunction with OpenWindows does not support pasting from x3270/S to OpenWindows applications and does not support the reverse video icon when output is pending in an iconified session. ======================================================================== >(I)91170. The new release of CAD expert is here Subject: CAD Expert 1.5 New with CAD Expert 1.5: o CAEDS v4 -"parametric" systems subset of "variational" systems o CADAM v3 r3 -great surfaces modeling enhancements! o microCADAM Plus & microCADAM 3D -competitive new features o POWER Gt graphics adapters -establishe new levels in visualization o CADAM Xstation networks performance data -13 Xstation/130 on 1 550! o and in case you've missed CAD Expert 1.4: o "Search" facility allows word search within any given topic o Valisys now included, plus Valisys graPHIGS Package o Detailed description of the GPC suite of standard tests o SPECmark performance multi-vendor comparison tables To receive an electronic copy of CAD Expert, at the PROFS prompt enter TOOLS SENDTO DALNESSC TOOLS CADINFO GET CADXPRT PACKAGE To automatically receive CAD Expert updates, at the PROFS prompt enter TOOLS SENDTO DALNESSC TOOLS CADINFO SUBSCRIBE CADXPRT PACKAGE With regards, Sandy Albu This utility contains a nice online /6000 quick reference and runs on DOS or on PCSIM. ======================================================================== >(U)91171. High Availability/6000 Folks, IBM announced a "near fault tolerant" RPQ for the RISC6000 yesterday. It is RPQ #P91085, the result of efforts between AWD and Media Industry. Thanks to all in Los Gatos (Anne and Lynn), Cambridge (George and co.), Somers (Vijay) and Austin (Tom, Rod and Jim). John Ranta (in Boston where I am passing out cigars...) ======================================================================== >(U)91172. Printing from AIX on an AADU attached PC This has been tested by H. Schuster and me with AADU 2.1. We got to the point where even another user could use the locally attached printer. It's easy and straightforward| A. Hoetzel ----- AIXONDOS FORUM appended at 17:40:48 on 91/08/23 GMT (by RVARGAS at CORV M1) Subject:AADU support for a locally attached printer Ref: Append at 22:13:23 on 91/08/23 GMT (by PATTYN at BLDVM4) >Requirement: Customer wants to print from AIX on PC (XT's & clone >286's) attached printers thru AADU. Customer is currently using AADU >version 1.0 and only uses the VT100 terminal emulator. Connection to >RISC System 6000 is via serial ports (about 25 terminals). This is >for a University and cost is a BIG consideration. >Any ideas or comments? I have been considering upgrading AADU to >2.1 and writing some DOS code to monitor a given AIX directory and >copying any file to the DOS printer when a file appears then erasing >it. This could be done from a bat file or requires a dedicated >terminal (print server). This could be easier than you think, if the vt100 emulator of AADU supports a feature called "transparent print". This feature allows the emulator to direct all it receives through the serial port to a parallel attached printer. You can determine this with the following script: ------------------------cut here-------------------------- #|/bin/ksh # test.sh # script for determining if a vt100 emulator supports transparent print. echo "0335ic" echo "This is test of the transparent print feature" echo "0334ic" exit 0 -----------------------cut here------------------------------ If VM changes the characters in the listing, the following are the sequences in the first and third echo lines: first: backslash zero three three opening-bracket five i backslash c third: backslash zero three three opening-bracket four i backslash c Try this from an AADU atached PC (with parallel printer, of course). If you get the message on hardcopy, you're in luck. If not, sorry. If you were lucky, then you can substitute a 'cat' instead of the second 'echo' and print files directly from the host to the printer. Furthermore, you can write a backend program (in a shell script) that allows you to queue files on the PC's printer (see AIXPRINT FORUM for details). Roger Vargas ======================================================================== >(I)91173. Async performance on the /6000 IBM INTERNAL USE ONLY Advanced Workstation Division International Technical Support Center Austin Dallas National Marketing and Technical Support Center 08/23/91 RISC SYSTEM/6000 ASYNC PERFORMANCE PURPOSE The intent of this document is twofold. The first section describes some of the differences between RAW I/O and CANONICAL (sometimes referred to as "cooked") I/O and surfaces performance and sizing implications of each method. All remaining sections cover the performance measurement and tuning of async ports whose usage is dedicated to RAW MODE file transfers. This document is not intended to be used as a guideline for sizing async requirements in a multi-user interactive environment. RISC SYSTEM/6000 RAW VERSUS CANONICAL (COOKED) ASYNC In AIX, as is the case with all UNIX systems, characters are processed one at a time. This approach to async I/O, unlike the 3270 block oriented protocol, has the potential to create a large amount of CPU overhead. AIX asynchronous I/O can be categorized as either RAW or CANONICAL. RAW refers to data that is not processed by the operating system and is merely sent unmodified to the application requiring the data. Canonical refers to data which is processed by the operating system for special character sequences (such as backspace, delete and many others). The canonical processing can be equated to a filter that pre-processes the input I/O data stream before it reaches the application and post-processes th e output stream produced by the application before it reaches the I/O device. One example of RAW mode async might be file transfers where the application does not care what characters are in the data stream. It merely transfers the data through the async ports without regard to special character sequences. Devices that are often handled in RAW mode are fax machines. Since modems are simply a transport medium, they can be used for either mode. Application interfaces to terminals, printers, and plotters frequently are also designed to have the operating system absorb the overhead of processing RAW device I/O into a CANONICAL I/O stream that complies with the virtual device interfaces used byt he application. Continuing the backspace example, AIX shell processes (ksh, sh csh, etc.) do not directly handle backspace characters. Instead, there is a process between the terminal driver and the kernel that buffers the I/O stream into lines of characters and performs other special character processing. It is here that the raw backspace is converted into the sequence "backspace space backspace" that is echoed back to the terminal. The erroneous character has been removed from the buffer that will eventually be sent to the shell whena carriage return or "enter" is typed. What the application receives is "what the user really meant". In evaluating system performance, the distinction between RAW and CANONICAL processing can become blurred because, while many applications run in RAW mode, the application itself internally processes the data stream. A better characterization of the loading can be obtained by carefully understanding the nature of the application. If significant processing is required of the data stream, a large amount of CPU utilization will be required for processing, regardless of whether the processing is done by the operating system or by the application. Other factors to consider are how much traffic each individual port will be required to handle and the total amount of expected traffic for the entire system. The measurements presented in this document apply for the most part to the realm of raw async file transfer. They can provide valuable guidance when configuring systems for high performance async data throughput, but are inappropriate when seeking to estimate the performance of the async adapters when sizing interactive terminal applications. Interactive applications typically operate in burst mode with much of the time spent waiting for user input. Consequently, the aggregate throughput is well withing the limits of what the async adapters and the CPU can support. For example, a 95 user RAMP-C benchmark running on a RISC System/6000 model 530, shows an overall average throughput of 5810 characters/sec for sends and 146 characters/sec for receives at 70% CPU utilization. The adapter resource required (throughput) for that benchmark does not exceed 10 percent of the sustained RAW mode file transfers indicated in Table 1! Clearly, the adapters will not be the bottleneck in that type of multi-user interactive environment. Specifications and presentation materials on multi-user, commercial benchmarks, such as RAMP-C, TPC-A, and the IBM office benchmark can be found on the HONE/IBMLink COMP database or the PEC tools disk at DALVM41B. The RISC System/6000 Quicksizer is also a valuable tool for configuring these types of systems. Async communication is often misunderstood and therefore appropriate decisions are often difficult to make. A report has been produced for those who may need additional information concerning RAW mode file transfer performance of the async adapters. It includes line charts, configurations and methods used to measure the performance. Also included are paragraphs containing an analysis of the measurements. A softcopy package containing the report and this FLASH (both in LIST3820 format) is available from the AIXIC tools disk on DALVM41B. The package can be retrieved by issuing the following command from your VM account: TOOLS SENDTO DALVM41B TOOLS AIXIC GET ASYNCXFR PACKAGE RISC SYSTEM/6000 RAW MODE ASYNC FILE TRANSFER PERFORMANCE The 8/16/64 and native asynchronous adapters were designed for servicing terminals and printers and therefore are optimized for output. Comparison of the send throughput versus the receive throughput for the various adapters consistently reflects this optimization. The throughput measurements in the following table were made using raw mode file transfers, i.e., an application characterized by a data stream with very little special character processing. Most interactive applications will have additional processing done by either the operating system or by the application itself. The measurements of sustained async output, Half Duplex send, shows significant CPU utilization, but do not indicate that the system is CPU constrained. The receive and full duplex file file transfers do indicate that the system has become CPU constrained. Users in interactive tty sessions may notice increased response times as the CPU is more utilized and becomes the pacing resource for the system. *------------------------------------------------------------------------* |Adapter| | Speed |Active|Throughput | CPU |Effective| | Type | Method |Kbits/sec|Lines | char/sec |Usage |Kbits/sec| |-------+-----------------+---------+------+-----------+-------+---------| |N/8/16 |H/Duplex Send (5)| 19.2 | 32 | 48900 | 35% | 15.3 | |-------+-----------------+---------+------+-----------+-------+---------| |N/8/16 |H/Duplex Send (5)| 38.4 | 32 | 78400 | 68% | 24.5 | |-------+-----------------+---------+------+-----------+-------+---------| |N/8/16 |H/Duplex Rec (6) | 19.2 | 6 | 11094 | 93% | 18.5 | |-------+-----------------+---------+------+-----------+-------+---------| |N/8/16 |H/Duplex Rec (6) | 38.4 | 4 | 10553 | 98% | 26.4 | |-------+-----------------+---------+------+-----------+-------+---------| |N/8/16 |F/Duplex (6) | 19.2 | 5 | 17629 | 89% | 17.6 | |-------+-----------------+---------+------+-----------+-------+---------| |N/8/16 |F/Duplex (6) | 38.4 | 3 | 17829 | 87% | 29.7 | |-------+-----------------+---------+------+-----------+-------+---------| |64(2,3)|H/Duplex Send (5)| 19.2 | 8/32 |13500/54500|6/25% |16.3/16.0| |-------+-----------------+---------+------+-----------+-------+---------| |64(2,3)|H/Duplex Send (5)| 38.4 | 6/24 |13500/54500|6/25% |22.0/21.0| |-------+-----------------+---------+------+-----------+-------+---------| |64(2,4)|H/Duplex Rec (7) | 19.2 | 5/10 |8500/19500 |44/100%|17.0/18.0| |-------+-----------------+---------+------+-----------+-------+---------| |64(2,4)|H/Duplex Rec (7) | 38.4 | 4/7 |8500/19500 |44/100%|22.0/22.5| |-------+-----------------+---------+------+-----------+-------+---------| |64(2,4)|F/Duplex (7) | 19.2 | 4/10 |12550/35800|35/100%|15.8/17.0| |-------+-----------------+---------+------+-----------+-------+---------| |64(2,4)|F/Duplex (7) | 38.4 | 3/7 |12550/35800|35/100%|19.5/19.5| *------------------------------------------------------------------------* Figure 1. RISC SYSTEM/6000 ASYNC file transfer performance (1) Note: (1) System under test was a model 530. (2) Measurements for the 64 port adapter are per concentrator box/per adapter . (3) Measurements made with 1 then 4 concentrator boxes. (4) Measurements made with 1 then 3 concentrator boxes. (5) NO flow control. (6) XON/XOFF software flow control. (7) RTS/CTS hardware flow control. PERFORMANCE TUNING THE ASYNC SYSTEM FOR FILE TRANSFER Depending upon the application, significant improvements to the current async system are possible today. o For the 8/16 and native port adapters, changing the receive trigger (rtrig) from the default value of 0 to a new value of 3 may significantly reduce the CPU usage for input operations (up to 60% for file transfer applications) because it allows few interrupts of the CPU. With this setting, the UART chip in the adapter produces an interrupt for every 14 bytes in the FIFO queue. The current default of, rtrig 0, interrupts the CPU once for every byte on the queue. rtrig 3 will become the default setting for future releases of the operating system. Note: This is not a Posix command and is unique to the 8/16 port adapters and the native ports. Example: /etc/tty/stty-rs rtrig 3 < /dev/ttyn o Maximize the value of vmin to conform to the application data block sizes. vmin is the minimum number of bytes that the system will attempt to read from the device in one operation. Changing vmin from the default value of 4 to the maximum of 255 will result in fewer read calls and may reduce CPU utilization by 15-20% for input file transfers. If vmin characters are available, they will all be read in one operation. If they are not available, the process will block waiting for the additional characters. To prevent an indefinite block on read, set vtime to some value greater than zero. (See the "How to Create a Fastport for File Transfers" section of this document). o The 64 port adapter is significantly more efficient in processing characters in raw mode than the 8/16 port adapters. Using a model 530 as an example, during half duplex receive, the 64 port adapter will process 193 characters/sec for 1% CPU utilization, while the 16 port adapter will process only 120 characters/sec (61% better). For half duplex send, the 64 port adapter will process 2200 characters/sec for 1% CPU utilization, while the 16 port adapter will process 1450 characters/sec (52% better). 8 and 16 port adapters and native serial ports are all serviced by the same device driver and consequently have similar performance characteristics. These adapters can support only 3 concurrent lines at 38.4 Kbaud or 6 concurrent lines at 19.2 Kbaud and then run out of CPU. Unlike the 64 port adapter, the effective baud rates track the line speeds quite well (even at 38.4 Kbaud). o The 64 port adapter running at 38.4 Kbaud will exhibit reduced performance. The effective baud rate with one line in use is 22.5 Kbaud and it drops off rapidly as more lines are added. The 16 port concentrator boxes for the 64 port adapters have a limited bandwidth and saturate easily at higher baud rates (3-4 lines at 38.4 Kbaud). After that, no additional throughput is possible unless additional concentrators are added. With all 64 ports concurrently in use, the effective baud rate drops to 8.8 Kbaud per line for transmit and 2.9 Kbaud per line for receive. Once the concentrator is saturated, adding more lines to the same box will decrease the performance of all ports connected. As an alternative, add another concentrator and continue until the next saturation point or until you have run out of CPU resource. o For raw mode sends where output translation is not needed, turn off the opost option in the Posix line discipline. This will help the CPU performance by reducing the output path length. For file transfer applications, which move large amounts of data through the async ports, this may reduce CPU utilization by as much as 300%. Example: stty -opost < /dev/ttyn (Reference Posix line discipline in InfoExplorer: opost option) o For input processing, use of the echo option is expensive because it increases the time required per character. Character echo is useful for canonical user input, because the user is able to see on his terminal the characters he is typing. Character echo is probably not necessary for most raw mode applications because either the application will take care of displaying the characters (as in vi) or there may be no reason at all to display the characters (file transfers). Example: stty -echo < /dev/ttyn (Reference Posix line discipline in InfoExplorer: echo option) o The 64 port adapter may exhibit data overruns at higher baud rates if XON/XOFF pacing is used. If RTS/CTS hardware pacing is used in conjunction with a 64 port adapter, there is no loss of data. For the 8/16 port adapters, using XON/XOFF flow control may be preferable, because it requires only 3 wires whereas hardware flow control may require 5-7 wires (cost difference). (Reference Posix line discipline in InfoExplorer: pacing control) If your application uses async for file transfer, or if you have a complicated async network, you may be able to get additional system configuration assistance from your AIX support staff. Individual ports and adapters can be optimized for file transfers. See the next section of this document for a shell script that implements most of the above tuning recommendations. A port configured in this manner requires 3-4 time less CPU than the default port configuration and gives significantly better overall performance. HOW TO CREATE A FASTPORT FOR FILE TRANSFERS 1. Create a tty for the port using SMIT with speed=38400 and login=disable. 2. Create the following shell script in a file named fastport.s. 3. Invoke with the command: fastport.s Example: fastport.s 0 to configure tty0 fastport.s : set -x sync;sync i=$1 if ( $i -le 100 ) then # set vmin=255 and vtime=0.5 secs stty -g < /dev/tty$i | awk 'BEGIN {FS=":";OFS=":"} {$5="ff";$6=5;print $0}' > foo stty ' cat foo ' < /dev/tty$i sleep 2 sync;sync # set the receive trigger to 3 (does not apply to the 64 port adapter!) /etc/tty/stty-rs rtrig 3 < /dev/tty$i sync;sync # set raw mode with minimal input and output processing stty -opost -icanon -isig -icrnl -echo -onlcr < /dev/tty$i sync;sync else echo usage is fastport.s fi Note: The set -x line of the shell script can be very useful in determining the point of failure if the program does not run successfully. It sets the shell option that causes each command line to be displayed before it executed. Generally, if subsequent commands are not displayed, then the last command displayed failed to execute properly. The set -x command also serves to synchronize the output returned by the command with the invocation of that command. Once the script is executing properly, the set -x command may be removed. GLOSSARY Async adapter: A printed circuit card which resides on the microchannel which provides for multiple asynchronous (e.g. RS232 or RS422) connections. Bandwidth: A measure of the amount of data a device can process, such as characters per second. The term is usually applied to limiting points in a hardware design such as data links or adapter cards. Baud: The rate of signal change on a teleprocessing line. Typically the number of bits per second transmitted on the line. Bit bucket: A connection, for purposes of this test report, which allows un-impeded outbound transmission of the data with no flow control restrictions. Cooked mode or Canonical processing: Data is processed according to a pre-defined set of rules. For example, shell commands. Concentrator box: For the RISC System/6000, the remote box, which, when used with the 64 port controller card provides for 16 RS232/RS422 connections. Sometimes called a "Fanout box". Device Driver: Software which defines and controls the interaction between the hardware and the computer operating system. Fanout box: A hardware connection which provides multiple asynchronous ports . Flow Control: Hardware or software mechanisms employed in data communication to turn off transmission when the receiving device is unable to store the data it is receiving. Sometimes referred to as handshaking, pacing, XON/XOFF or RTS/CTS flow control. Full Duplex: Simultaneous independent transmission in both directions. Half Duplex: A circuit designed for transmission in either direction but not both directions simultaneously. Handshaking: See Flow Control. Line Discipline: The asynchronous communication user interface for a TTY. Examples are the Posix and Berkeley line disciplines. Note: Posix is currently supported. Pacing: See Flow Control. Port: An asynchronous connection to the computer, or TTY line. Raw mode: Data is treated as a continuous stream without consideration of the data's logical structure. Also, erase and kill processing are disabled. RTS/CTS: A type of hardware flow control. When the receiving device is unable to store the data it is receiving, it turns off its RTS (Ready To Send) line which is connected to the sending device's CTS (Clear To Send) line. The sending device then discontinues its transmission. When the receiving device is again able to accept data, it turns on its RTS line, which triggers renewed transmissions fromt the sending device. Throughput: A measure of the amount of data a device can either transmit or receive per second. The term may be applied to a single port, multiple ports or an entire adapter card. TTY line: An asynchronous connection to the computer, or port. UART: Universal Asynchronous Receiver Transmitter. A device which both receives and transmits serial data and converts it to a parallel form usable by the bus interface. XON/XOFF: A type of software flow control. When the receiving device is unable to store the data it is receiving, it sends a preset signal (XOFF) to the transmitting device. When it is again ready to accept data, it sends another preset signal (XON) to the transmitting device. (RAH) This is a very helpful package if you have to deal with Async I/O. Issue a: TOOLS SENDTO DALVM41B TOOLS AIXIC GET ASYNCXFR PACKAGE The ASYNCXFR package consists of three documents: ASYNCDOC TRS2830 ASYNFLSH TRS3820 ASYNCXFR README ASYNCDOC is a 40 page report that includes line charts, configurations and methods used to measure the performance of RAW MODE ASYNC FILE TRANSFERS utilizing the native, 8/16 port and 64 port async adapters on the RISC System/6000. Also included are paragraphs containing an analysis of the measurements. The unpacked version of the document is slightly more than 71 MB long, so ensure that your disk has enough room to hold it. ASYNFLSH is a softcopy of the FLASH that summarizes the larger 40 page document. It includes sections on Raw versus Canonical (Cooked) Async, File Transfer Performance, Performance Tuning the Async System, and instructions on how to create a fastport for file transfers. The unpacked version of the document is slightly less than 1.3 MB long. ======================================================================== ======================================================================== Brain fried -- Core dumped >91.09.10 Table of contents: (U)91174. Wyse Terminals for the RISC System/6000 (I)91175. People searching for references (U)91176. More on Remote Backups (U)91177. Accessing BookManager on AIX (U)91178. Bootable Backups - Dallas Flash (U)91179. Automatic restart of AIX 3.1 after crash (U)91180. Correction to previous tip number 91140 about X and NLS ======================================================================== >(U)91174. Wyse Terminals for the RISC System/6000 Wyse Wy-370 Color ASCII Terminal connected to RISC/ 6000 Wyse is offering an ASCII-Terminal which emulates many other terminals (e.g. VT220), uses colors to display attributes, has some graphical capabilities (4014-Emulation with a resolution of 640*480points), and can be configured by means of a very comfortable setup . I tested this terminal during the last days in the following configurations: 1. The terminal was connected both to a RS232 and RS422 interface 2. An "International Enhanced PC-Style Keyboard- U.K. English" or an "International Enhanced PC-Style Keyboard- German" was attached. In all configurations the terminal worked perfectly with the RISC/ 6000 (ksh, vi, smit) when we used the TERMINFO file delivered by Wyse. To get a complete terminfo source for WYSE terminals use one of the following TOOLS commands: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET WYSE TIZ or TOOLS SENDTO DLVM41B IBMPC AIXDOC GET WYSE TIZ Download the file in binary to /usr/lib/terminfo/wyse.ti.Z run uncompress wyse.ti and then tic wyse.ti We got this file with a wyse terminal. Please be aware that all those applications which use their own terminal description files will not run properly (HCON, INed, PCSIM, JSB Multiview). I am planning to write an AIX Tip giving full details of the hardware and software setup used. Dr. Gerhard Hoffmann, AIX FSC Germany ======================================================================== >(I)91175. People searching for references A lot of people are searching for reference installations. Here is a suggestion: Have you looked in the COMP database on HONE ? It contains all kind of WIN stories. Mainly USA appends, but the COMP people are waiting your WIN stories from all over the world. Browse through it and you'll be impress at how we sell those machines. When you WIN a case, just send a short story, a page or so, to this account NADIA AT CPHVM4 It'll take some days to proof it and you'll find your story in COMP database ACCESSIBLE by everybody. Anne SERRE - aser at chvm1 - Becoming a COMP addict. ======================================================================== >(U)91176. More on Remote Backups Most people complain that there is no way of doing remote backups. To counter that here are some tips from the German NSC/SPOC: There is only one small restriction: Multivolume backups are not possible accross the network because the device drivers do not report the tape change request back via pipes. Here we go: The machine "49ers" has a tape and the machine "jets" wants to backup something on it. Mount tape on 49ers. On jets: find . -print backup -iqvf- rsh 49ers "dd obs=100b of=/dev/rmt0" Check: rsh 49ers "dd if=/dev/rmt0 ibs=100b" restore -Tqf- Restore: rsh 49ers "dd if=/dev/rmt0 ibs=100b" restore -xqf- Notes: You could use tar or another backup program as well. You need the correct $HOME/.rhosts or /etc/hosts.equiv file on the target machine to make rsh work. See the info entry on rsh for more details. This was old known info, wasn't it? Now for something tricky, like system backups: On jets: mknod /tmp/pipe p mkszfile cat /tmp/pipe rsh 49ers "dd of=/dev/rmt0 obs=100b" & mksysb /tmp/pipe Notes: To restore you either need a real tape on jets or you load the tape on disk for a network install. Or you get really fancy and install from the tape of a network install server: Warning, enter at your own risc: Prepare the following on the installserver: cd /u/netinst/scripts edit the file getdb and search for xargs: you should find the following lines: xargs ls -ld 2> /dev/null while read fmode garb garb garb fsize garb garb garb fn At the end of the "while" line you have to add another variable "garb" while read fmode garb garb garb fsize garb garb garb fn garb Save it and edit the file sendfssz: At the end of the file you find the following "if" block: if ! -f "$bosobjname" then exit 1 fi Replacwe the "-f" falg with the "-r" flag: if ! -r "$bosobjname" Lets's assume the directory /usr/sys/preload contains the installation immage s (must be listed in /u/netinst/db/choices). Now do the following link: ln -l /dev/rmt0 /usr/sys/preload/bos.objrmt Now select /usr/sys/preload/bos.objrmt for installation at the clients installation menu. Beware, the mods in the script above might need to be changed for operating system levels other than 3.1.5. MfG. B. Zeller (hubertrs530.ncs.mainz.ibm.com) ======================================================================== >(U)91177. Accessing BookManager on AIX ACCESSING BOOKMANAGER SOFTCOPY ON AIX ------------------------------------- IBM strategy is to ship all product information in softcopy form. The stategic product for SAA softcopy documentation is BookManager. Already many IBM products are shipping softcopy information in BookManager format (VM/ESA, CICS, AS/400, MVS, VSE, DPPX and many others), and many more are planning to do so in the future. Much of this information is available on CD-ROM discs. Because BookManager only runs on MVS, VM, DOS, and OS/2 this information is not currently accessible to AIX users. However, both the RISC System/6000 and AIX PS/2 provide PC-DOS simulators that can be used to run the BookManager READ/DOS product. There are also PC simulator programs that will run READ/DOS on non-IBM platforms such as Apple Macintosh, HP, Sun, and others. I have written instructions for using BookManager with the RISC System/6000 PCSIM program and PS/2 AIX DOS Merge programs. The RISC System instructions also explain how to use a local or remote CD-ROM player. BookManager should also be able to access CD-ROMs on an AIX PS/2, but we have not been able to get the CD-ROM device driver as of the writing of these instructions. Both implementations can be installed on a server machine and accessed by remote clients. The easiest way to do this is with the rexec facility of TCP/IP along with the remote display facility of X Windows. For example, you could set up a RISC System/6000 with PCSIM and BookManager. You can then put a CD-ROM such as the VM/ESA documentation disc in the CD-ROM drive, thus making the VM/ESA documentation available from any client in your network with X Windows capability. For the instructions on setting up a RISC System/6000 or AIX PS/2 with BookManager READ/DOS, please use the following command: REQUEST AIXBKMGR PACKAGE FROM KIOSK AT KGNVMZ For further information, please contact David Silverman, AGMAN at KGNVMZ. Note from the editor: I tried mounting DOS stuff in HIGH SIERRA format on AIX. No success so far. Looks like not all HIGH SIERRA disks are equal. You might need update 2006 to make this work. ======================================================================== >(U)91178. Bootable Backups - Dallas Flash Document ID G010130 TITLE: DSSC FLASH 1132 WARNING: Dallas National Marketing and Technical Support Center Document Number F1132 09/03/91 Dallas National Marketing and Technical Support IBM Southlake DNM&TSC F1132 09/03/91 WARNING: PROBLEM INSTALLING HIGH DENSITY MULTIPLE VOLUME BOOTABLE BACKUP TAPES ****************************** WARNING ***************************** You will not be able to install MULTIPLE volume BOOTABLE tape backups created in HIGH DENSITY format. ********************************************************************** Date: 8/20/91 INTRODUCTION This document is not intended to replace any existing documentation. It is a supplement that provides information necessary to create, and reinstall multiple volume 1/4" tape backups. You can create and reinstall a SINGLE volume BOOTABLE stacked tape in high density without error. This problem has not been reported, or tested, using 8MM tapes since most 8MM backups are single volume. ERROR MESSAGE An error has been discovered in the restore process when restoring multiple volumes using bootable stacked tapes. The error message only occurs when using a high density tape device, such as /dev/rmt0.1 The following error message is displayed at the end of the first volume: READ ERROR: Media Surface Error Assuming Zeros and continuing The system never prompts the user to mount the second volume. This problem has been reported to defect support, PMR # 6X814 and PMR # 6X282. You can create and reinstall a SINGLE volume BOOTABLE stacked tape in high density without error. INSTALLATION OF MULTIPLE VOLUME HIGH DENSITY BACKUP TAPES The following procedures will show you how to get around the problem if the only backup you have is multiple volume, bootable, AND created in high density. You WILL NOT be able to restore this backup without recreating the INSTALL/MAINT diskette. You will need to edit the boot2, inslist, and bosmenus files prior to recreating the INSTALL/MAINT diskette. Use the following commands to change the inslist and boot2 files: cd /usr/lpp/bosinst/diskette echo ./bin/tctl >> inslist echo ./bin/tctl >> boot2 To change the bosmenus file: cd /usr/lpp/bosinst cp bosmenus bosmenus.orig Edit bosmenus Search for the following statement: *) # restore ./.fs.size fom chosen device. if ( 4 -ne "$bootype" ) then restbyname -xqf$instdev ./.fs.size fi ;; esac Add the next two lines AFTER 'esac' from the above statement: # Moving the tape forward for high density restore here. tctl fsf 3 RECREATE THE INSTALL/MAINT DISKETTE If you are using AIX Version 3.1.3, Perform the following: (A formatted diskette must be in the drive.) Login as root cd /usr/lpp/bosinst cp bosmenus bosmenus.save cp bosrest bosrest.save sed -e 's/.5 -p//' < bosmenus.save > bosmenus sed -e 's/.5 -C/ -C' < bosrest.save > bosrest /usr/lpp/bosinst/diskette/mkinstdskt /usr/bin/bosinst.image dd if=/usr/bin/bosdis.image of=/dev/rfd0 ibs=90b obs=90b conv=sync If you are using AIX Version 3.1.5, perform the following: (A formatted diskette must be in the drive.) Login as root /usr/lpp/bosinst/diskette/mkinstdskt If you are using a version earlier than AIX Version 3.1.3, Please see IWSYS Flash 9061 Installation Overview and Tips for AIX V3.1 on the RISC System/6000. CREATING BACKUP TAPES This section shows how to create backup tapes that will not encounter this error by referencing two existing documents: Item 6VPBN Document ID Q550089 HOWTO AIX: Creating a bootable and re-installable backup tape of your complete Risc System/6000 system configuration FLASH 9061 DOCUMENT ID G042806 Installation overview and tips for AIX V3.1 on the Risc System/6000 This document will contain three different methods for creating multiple volume tape backups: 1. CREATING MULTIPLE VOLUME BACKUP TAPES: This section will discuss the most common way to backup your system. The user may install this type of backup onto different RISC System/6000's as long as there is sufficient disk space available. 2. CREATING LOW DENSITY MULTIPLE VOLUME BOOTABLE BACKUP TAPES: This section will discuss how to create multiple volume bootable tape backups. This backup MUST use LOW DENSITY. This backup is used to reinstall your existing system should a catastrophic failure occur. 3. CREATING HIGH DENSITY MULTIPLE VOLUME BACKUP TAPES THAT CONTAIN THE DEVICE CONFIGURATION FILES: This section will discuss how to create mksysb backup tapes that contain the system's device configuration (ODM) files. This type of backup tape is to be used in conjunction with the Bosboot, Console, and Install/Maint diskettes, as it is not a bootable tape. 1. CREATING MULTIPLE VOLUME BACKUP TAPES: The preferred method of creating multiple volume tape backups is to create the Bosboot, Console, and Installation/Maintenance diskettes, then create the file system size file by running mkszfile, then backup the files to tape using mksysb. The steps necessary to create this type of backup can be found in Flash 9061, Installation Overview and Tips for AIX V3.1 on the Risc System/6000. Section 3.2.0 Creating IPL diskettes Section 3.3.0 Creating the Tape Perform Steps 1,2,3,4,8 You can use high density when performing this backup. 2. CREATING LOW DENSITY MULTIPLE VOLUME BOOTABLE BACKUP TAPES: If you have printed Document ID Q550089, HOWTO AIX: Creating a bootable and re-installable backup tape of your complete RISC System/6000 configuration, prior to 08/26/91, you will need to print the document again. The device name has been changed in the following lines in the sysback script: # Create bosboot image on tape dd if=/usr/bin/tape.image of=/dev/$TAPE.5 bs=512 conv=sync # Put install files on tape dd if=/usr/bin/bosinst.image of=/dev/$TAPE.5 bs=512 conv=sync dd if=/bootrec of=/dev/$TAPE.5 bs=512 conv=sync # Backup System mksysb /dev/$TAPE.4 NOTICE: The /dev/$TAPE.* has changed in each of these lines. 3. CREATING HIGH DENSITY MULTIPLE VOLUME BACKUP TAPES THAT CONTAIN THE DEVICE CONFIGURATION FILES: If you would like to create high density multiple volume backup that contains the complete system configuration, perform the following: Create IPL diskettes from section 3.2.0 Creating IPL diskettes found in Flash 9061, Installation Overview and Tips for AIX V3.1 for the Risc System/6000. Then follow the directions in: HOWTO AIX: Creating a bootable and re-installable backup tape of your complete Risc System/6000 configuration. Create the sysback script (This script is intended for disaster recovery, not cloning systems.) By commenting out the following lines, the script you are creating will make a backup of the system configuration data base (ODM) and create the backup image on tape. The tapes created will NOT be bootable. # Create bosboot image on tape. # bosboot -m -d /dev/$TAPE -p /usr/bin/tape.proto -f /usr/bin/tape.fs -b /usr/bin/tape.image 2>/dev/null # dd if=/usr/bin/tape.image of=/dev/$TAPE.5 bs=512 conv=sync # Put install files on tape # /usr/lpp/bosinst/diskette/mkinstdskt /usr/bin/bosinst.image # dd if=/usr/bin/bosinst.image of=/dev/$TAPE.5 bs=512 conv=sync # dd if=/bootrec of=/dev/$TAPE.5 bs=512 conv=sync Change the tape device by editing the following line: mksysb /dev/$TAPE.4 to look like: mksysb /dev/$TAPE ======================================================================== >(U)91179. Automatic restart of AIX 3.1 after crash If you want to restart your AIX system automatically after a system crash, yo u need to change an attribute in the sys0 device: >From woanexeter.austin.ibm.com (Ronald S Woan): This is user configurable as the autorestart attribute of sys0. To see what yours is set to "lsattr -E -l sys0". You can use "chdev -l sys 0 -a autorestart=true" or something to that effect to set it to true. ======================================================================== >(U)91180. Correction to previous tip number 91140 about X and NLS: :> >91140. X color resources and NLS :> :> If you have problems with standard X programs that want to use standard :> english color resource names on a system that has been delivered with NLS, :> then the following steps might help you: :> :> Basically the NLS and the English color tables are merged and then a new :> RGB database is created. :> The following example assumes a German NLS system. :> :> cd /usr/lib/X11 :> cat ./En_US/rgb.txt ./Gr_GR/rgb.txt > rgb.all :> ./rgb rgb < rgb.all cp rgb.dir rgb.pag Gr_GR :> :> After the next start of X everything should work, with German and English :> color names. Sorry, I forgot the copy command. ======================================================================== ======================================================================== DEC is now into RAP music instead of products: NEW YORK (UPI) -- A creative session was held today at a major New York PR firm, to formulate a new corporate message for Digital Equipment Corp. that reflects the company's new direction promoting and supporting computing industry standards. The shopworn phrase "Digital has it now" will be replaced by a new tag line that is more contemporary, and is tied to DEC's new adherence to industry standards. "Digital's hip to the standards thing" will become the $11.5 billion company's new-image slogan. In a radical departure from it's traditionally staid advertising approach, the company will produce a television ad built around a rap music theme played out in a rapidly changing sequence of office and engineering scenes. In a parody of the commonly used product nomenclature, the video itself is referred to as "a mythical Digital product called DECrap." The lyrics to the rap video are: "Digital's Hip to the Standards Thing" ====================================== I heard some news just the other day It sounded kinda strange and I said, "No way!" But I heard it again from another source It mighta made sense and I said, "Of course!" Now computer biz has a lotta confusion 'Cause operating systems abound in profusion. But there's a whole new wave in data processing Now that Digital's hip to the standards thing. (chorus) Digital's hip to the standards thing! Digital's hip to the standards thing! Way back when a long time ago IBM owned the whole show. But other dudes saw this proprietary mess And formed committees to find out what's best. Some went their own way and built their own software But users were perturbed, "It's just a different nightmare." So they got together to look over the picks Put their down their money on good 'ol UNIX (chorus) Digital's hip to the standards thing! Digital's hip to the standards thing! Now Digital always kept their users in mind And pushed VMS as the best of the kind. A lotta folks agreed but kept askin' for UNIX support, "We gotta have more!" Soon DEC saw the light and decided to give UNIX to the masses, (sorta live and let live). So DEC's ridin' the wave ahead of the rest On a backplane bogie board on top of the crest. No doubt about it DEC's sprouted its wings 'Cause Digital's hip to the standards thing. (chorus) Digital's hip to the standards thing! Digital's hip to the standards thing! >91.09.19 Table of contents: (I)91181. Where do I find reference customers in Germany? (I)91182. AIX/ESA* Presentation Guide Available On MKTTOOLS (U)91183. New TCP/IP for DOS and OS/2 (U)91184. How to tell NFS clients about a server shutdown. (I)91185. REBUTTAL OF POOR RISC SYSTEM/6000 MULTITASKING PERFORMANCE CLAIMS (I)91186. AIX geoGPG/6000 Performance Enhanced, Update Available (I)91187. New numerical performance tuning guide (I)91188. Developement wants input on SMIT printer configuration (I)91189. A description of PEX (PHIGS on X) (I)91190. More info about the 3151 (I)91191. What do you need to debug SNA connections (I)91192. HA/6000 forum available ======================================================================== >(I)91181. Where do I find reference customers in Germany? In the German section of HONE you can find reference Customers in AWB, the applications database for the /6000. There is no WIN shortpath for AIX reference customers. ======================================================================== >(I)91182. AIX/ESA* Presentation Guide Available On MKTTOOLS September 11, 1991 IBM today announced its intent to deliver Advanced Interactive Executive/Enterprise System Architecture* (AIX/ESA)* for customers wanting a mainframe version of UNIX**, an open operating system widely used for scientific, technical and commercial applications. An AIX/ESA* Overview presentation guide is available and was shipped in the branch box for today's announcement. This presentation guide contains both color foils and a script for your use. You can also order the presentation guide from MKTTOOLS by entering the following command on the OV/PROFS command line: TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET AIXG PACKAGE Questions on the marketing guide and AIX/ESA* can be directed to: AIXESA at DFWVM04 NEED TO SCHEDULE A BRIEFING FOR YOUR CUSTOMER? The AIX* Enterprise Marketing Center, Dallas, works directly with the account team to tailor briefings to your customer's requirements. The AIX Enterprise Marketing Center can discuss AIX implementation across the enterprise on workstations and host processors. Topics presented to your customer are reinforced with demos. For more information on Customer Briefings, contact: AIXMIC at DFWVM03  * Advanced Interactive Executive/Enterprise System Architecture and AIX/ESA are trademarks or registered trademarks of International Business Machines, Inc. ** UNIX is a registered trademark of UNIX Systems Laboratories, Inc. ======================================================================== >(U)91183. New TCP/IP for DOS and OS/2 P/N 02G7090 TCP/IP V2.0 for DOS P/N 02G7091 TCP/IP V2.0 for DOS - Programmers Tool Kit P/N 02G7092 TCP/IP V2.0 for DOS - NFS Kit See PLET ZP91-0519 Will be available in November. With our own NFS on DOS we will hopefully be able to scrap AADU| 5798-RXW 02G6982 TCP/IP Version 1.2 for OS/2 Base 02G6969 Extended Connectivity (X.25) 02G6970 Network File System (NFS) 02G6980 X Window System 02G6984 Programmers' Toolkit 02G6983 Total Kit(w/o Toolkit) 02G6878 Source |||| 10G4413 Upgrade (No Source) See PLET ZP91-0528 Will be available in November. This includes an X11.4 server and an NFS server, not just NFS client function s. With this functionality you could NFS serve your DOS machines with an OS/2 server or even mount an OS/2 filesystem on AIX| ======================================================================== >(U)91184. How to tell NFS clients about a server shutdown. If you want to shutdown an NFS server then you probably want to tell all your NFS clients first. The following script will send a string to all machines that have an NFS mount from the server: #|/bin/ksh # write a message to all machines that nfs mount something from here. # afx 9/91 msg="$*" if -z "$msg" then echo "usage: $0 message" echo "writes a message to all machines that have mounts from "`hostname -s ` exit 5 fi # get the list of machines from the showmount command # get the name only, sort it and get only one entry per machine machines=`/usr/etc/showmount -acut -f1 -d: sortuniq` # tell all machines for i in $machines do echo "Notifying $i" echo "$msg" /usr/etc/rwall $i & done exit 0 ###### For the 3270 impaired: ` backquote ' single quote pipe open square bracket close square bracket ======================================================================== >(I)91185. REBUTTAL OF POOR RISC SYSTEM/6000 MULTITASKING PERFORMANCE CLAIMS September 16, 1991 Rebuttal of Poor RISC System/6000 Multitasking Performance Claims by Personal Workstation Magazine In the following Personal Workstation magazine articles: RISC-y Business - December 1990 HP 9000 Series 720: Performance update - May 1991 Personal Workstation Magazine (formerly MIPS Magazine) published benchmark results which, it purported, showed that the RISC System/6000 architecture does not perform well on multitasking workloads. While Personal Workstation has ceased publication, this past summer, the damage was done and many customers remember the Multitasking issues generated by these articles. IBM Advance Workstation Division has rerun the benchmarks and determined the magazines results to be incorrect and misleading, particularly with respect to its comparison of the RISC System/6000 architecture with that of the new HP 9000 Series 700 ("Snake") architecture. The rebuttal can be found on the PEC database. To receive the presentation file enter the following on the PROFS command line: TOOLS SENDTO DALVM41B TOOLS PEC GET PWREBUT PACKAGE You will receive the file and instructions as to how to print it. PEC "how to" questions can be sent to PEC at DALVM41B Marketing contact AARTALE at RHQVM05 ======================================================================== >(I)91186. AIX geoGPG/6000 Performance Enhanced, Update Available September 13, 1991 AIX geoGPG/6000 update Version 1.1.0.1 is now available. The new version provides significant performance improvements over the initial PID Version 1.1 especially for graphic draw times - as much as 35% faster. The update has been automatically sent to all geoGPG-installed customers. Customers and IBM locations currently running geoGPG should consider this update. If you need a copy, enter the following commands on the OV/PROFS command line: TOOLS SENDTO HOUVMUI TOOLS IBMGIS GET GEOPTF1 PACKAGE TOOLS SENDTO HOUVMUI TOOLS IBMGIS GET DSK1101A PACKAGE TOOLS SENDTO HOUVMUI TOOLS IBMGIS GET DSK1101B PACKAGE Instructions for downloading and reconstructing the two fix diskettes are included in the package. The following timing comparisons were done at the GIS Solution Center in Houston: ------------------ Response Times (in seconds) --------------------- geoGPG 1.1 geoGPG 1.1.0.1 M520 M520 M530 ----------- --------------- RUNGPG 30.0 26.9 23.1 LOAD/DISPLAY WORKSPACE 18.3 12.0 11.2 ADD POLE 1.3 0.9 0.9 ZOOM IN/OUT 0.8 0.7 0.7 DRAW WORKSPACE scale = 7400 13.3 7.9 6.8 scale = 3700 11.8 7.7 6.1 scale = 2400 9.6 6.7 5.9 scale = 1850 8.8 6.4 3.9 scale = 1200 6.0 4.9 4.1 scale = 600 8.1 5.6 5.1 scale = 300 7.7 3.7 3.4 scale = 150 4.0 2.5 2.5 scale = 75 2.7 1.8 1.7 ------ ------ ------ AVERAGE DRAW TIME 8.0 5.2 3.7 Measurements were taken for a selected set of geoGPG transactions on two IBM RISC System/6000 processors, Model 520 and Model 530. Response times for different versions were compared (V.1.1 times for Model 530 were not available.) Times were measured via stop watch using the Starter Set and the GPGSTART workspace distributed with the geoGPG product. All times were in a single-user environment. Each processor contained 32MB of memory. The Model 520 used a Color Graphics adapter; the Model 530 a High Performance 8-bit 3D Color Graphics Processor. Questions regarding the update package may be sent to Oskar Cerbins, T/L 260-3229 or 713/335-3229 or HOUVMUI(cerbins). ======================================================================== >(I)91187. New numerical performance tuning guide IBM RISC SYSTEM/6000 Model 550 ACHIEVES 73 Mflops| Announcing Version 2 of Ron Bell's Tuning Guide for FORTRAN and C Published as GG24-3611-01 This manual gives detailed guidance on how to tune numerically intensive FORTRAN or C programs on RISC System/6000 to achieve maximum performance levels. Many NIC codes can be run at Mflops rates much higher than the officially quoted LINPACK figures. For example, the official LINPACK figure for a model 550 is 25.2 Mflops. If, however, you tune the LINPACK code using the techniques described in the guide, then exactly the same 100x100 problem runs at 46 Mflops. If this tuned code is applied to the LINPACK 1000x1000 problem (that is the 'TPP' - Towards Peak Performance - problem) then a rate of 57 Mflops is achieved. ESSL (the IBM Engineering/Scientific Subroutine Library) uses an even higher level of tuning and pushes TPP performance to 70 Mflops. (Note: the official TPP figure in the Dongarra Report is 62 Mflops for a 550, but this should be updated in the future to reflect the data from ESSL.) Other codes can achieve even greater speeds and the Guide describes how to code a simple matrix multiply routine in standard FORTRAN which achieves 73 Mflops on a Model 550 - close to the theoretical peak rate of 83 Mflops. Version 2 of the Guide is a significant update on the original. Performance data is provided for the Model 550 as well as the 530, and there are chapters on ESSL and experience with both of the FORTRAN Preprocessors that come with the XL FORTRAN Version 2.2 compiler. (XLF V2.1 is available now: 2.2 has a GA of October, 1991 in the USA.) The guide will be orderable in hardcopy very soon as GG24-3611-01. Before ordering, check that the -01 version is available rather than the original -00. Softcopy is available on the STCEMEA and IBMUNIX tools disks. There are two files: GG243611 SCRIPT which requires BookMaster to format, and GG243611 LIST3820 which is already scripted and printable on a 3820. To obtain a copy of these, issue one of the following TOOLS commands: TOOLS SENDTO EHQVM1 ZTOOLS STCEMEA GET GG243611 LIST3820 or TOOLS SENDTO YKTVMH3 IBMUNIX IBMUNIX GET GG243611 LIST3820 In the UK, copies are also available on TSINFO on UMIS. PLease address any queries on the Guide to the author, Ron Bell, BELLRA at BASVM1. ======================================================================== >(I)91188. Developement wants input on SMIT printer configuration We in development are beginning to look at ways to improve the AIX v.3 SMIT interface for configuring printers and printer queues. We're open to any comments or criticisms of the current SMIT interface, and suggestions for improving ease of use and functionality. Please append to AIXPRINT FORUM or send mail to AUSVMQ(YODER). Regards, AIX printer development ======================================================================== >(I)91189. A description of PEX (PHIGS on X) As promised (or threatened), I'm making the paper that goes along with the PEX discussion at the graPHIGS User's Group Workshop available by request. Issue the following command from a CMS prompt: REQUEST PEXGPUG FROM SCHULTZ AT KGNVMY The paper is rather introductory in nature. I'd welcome any feedback so I can make it more useful. Abstract: This paper describes Pex, a X Window System protocol extension that enables 3D graphics. This description includes explanations of how the X server, equipped with a Pex extension, can accomplish advanced 3D rendering. This paper also addresses issues such as PHIGS implementation with Pex, client-side versus server-side retained graphic data, and implications of immediate-mode graphics with Pex. Karl Schultz AWD Graphics Systems / KGL graPHIGS Development ======================================================================== >(I)91190. More info about the 3151 Gary Carlson, the 3151 guy from Boca, asked me to post the following information here: If you have 3151 questions, you can have information sent directly to your VM node/ID simply by issuing the following command from VM: tell 3151 at BCRVM1 request You will receive information on what 3151 information you can request additional information on. Brad Konopik "I'm not a programmer, but I play one on TV" ======================================================================== >(I)91191. What do you need to debug SNA connections The guys from defect support have put together a list of things that should b e done when trying to report a SNA defect. Their ToDo list contains all the steps that are necessary to do traces and so on. We have an English and a German version available. Get it with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET SNADEBUG ANLEIT for the German version on the Munich disk. or TOOLS SENDTO DALVM41B AIXDOC GET SNADEBUG GUIDE for the English version on the US disk. Both versiona are available on both disks. ======================================================================== >(I)91192. HA/6000 forum available For the discussion of HA/6000 (High Availability /6000) check the HA6000 FORUM on IBMUNIX. ======================================================================== ======================================================================== God is real, unless declared integer. >91.10.01 Table of contents: (U)91193. System Backup / Restore troubles (I)91194. Demo code available for new TCP/IP Products (I)91195. New AIX management functions called "ROSE" available (U)91196. Printing for Fun and Profit Under AIX V3 (GG24-3570) Now Available (U)91197. Commandline Editing in the Korn Shell with Cursor Keys (I)91198. Graphics bug in the GTO and 2007 PTF (U)91199. New AIX Family Catalog now in Mechanicsburg (I)91200. XonDOS Corrective Service Fix (U)91201. OSIMF/6000 problem fix / missing DLC ======================================================================== >(U)91193. System Backup / Restore troubles If you run mksysb (SMIT SYDTEM BACKUP) then not everything is really saved and restored. Some device definitions are missing. SETI document OZSQ550089 contains two scripts that circumvent this problem. The following two scrips are slightly modified versions of those from the German Defect Support Group (H.-G.Stegelmann). There should be at least 8MB free in /usr before running the sysbackup script. Another problem is that multiple tape backups can not be made in high densit y on the QIC 150 tape. That's why the script writes in low density (120MB instead of 150MB). ###### For the 3270 impaired a translation table: ` backquote ' single quote pipe open square bracket close square bracket open curly brace close curly brace ^ caret tilde & ampersand -------------------- sysbackup -------------------- #|/bin/ksh # /bin/sysback - Save configuration and create bootable install tape # NOTE: Refer HONE entry ITEM 6VPBN, DOCNO OZSQ550089 tput clear echo "" echo $0 " This script creates a bootable system image on tape " echo "" echo $0 " Checking free space " echo "" df -v /tmp echo "" echo $0 " /tmp needs about 8M for building blv.image " echo $0 " Is amount of free space sufficient? y/n " read ANSWER case $ANSWER in y) continue;; *) exit;; esac TAPE=rmt0 # Make copy of old config echo $0 " Make copy of old config " mkdir /u/config 2>/dev/null cp /etc/objrepos/Cu* /u/config cp /etc/filesystems /u/config find /dev -print backup -iqf/u/config/devices 2>/dev/null chdev -l $TAPE -a block_size=512 # Create bosboot image on tape echo $0 " Create bosboot image on tape " bosboot -m -d /dev/$TAPE -p /usr/bin/tape.proto -f /usr/bin/tape.fs -b /usr/b in/tape.image 2>/dev/null dd if=/usr/bin/tape.image of=/dev/$TAPE.5 bs=512 conv=sync # Put install files on tape echo $0 " Put install files on tape " /usr/lpp/bosinst/diskette/mkinstdskt /usr/bin/bosinst.image dd if=/usr/bin/bosinst.image of=/dev/$TAPE.5 bs=512 conv=sync dd if=/bootrec of=/dev/$TAPE.5 bs=512 conv=sync # Backup system echo $0 " Backup system " echo $0 " Making Sizefile" mkszfile echo $0 " Running mksysb " mksysb /dev/$TAPE.4 -------------------- sysrestore --------------------- #|/bin/ksh # /bin/sysrest - Restore and resync configuration database # NOTE: Refer HONE entry ITEM 6VPBN, DOCNO OZSQ550089 PV=/dev/ipldevice # Keep a copy of current configuration echo $0 " Keep a copy of current configuration " mkdir /tmp/configold odmget -q attribute=pvid CuAt > /u/config/pvids cp /etc/objrepos/Cu* /tmp/configold # Restore old configuration echo $0 " Restore old configuration " echo $0 " Copying /u/config/Cu* to /etc/objrepos ... " cp /u/config/Cu* /etc/objrepos echo $0 " Copying /u/config/filesystems to /etc ... " cp /u/config/filesystems /etc echo $0 " Odmdeleting...attribute=pvid ............. " odmdelete -o CuAt -q attribute=pvid echo $0 " Odmadd /u/config/pvids ................... " odmadd /u/config/pvids echo $0 " Restore /u/config/devices ................ " restore -xqvf/u/config/devices # Delete root volume group from ODM echo $0 " Delete root volume group from ODM " lqueryvg -p $PV -L cut -c22-80 cut -d" " -f1 while read LV do odmdelete -q "name = $LV" -o CuAt odmdelete -q "value3 = $LV" -o CuDvDr done # Attributes echo $0 "Deleting Attributes " odmdelete -q "name = rootvg" -o CuAt # Decices echo $0 " Deleting Devices " odmdelete -q "parent = rootvg" -o CuDv odmdelete -q "name = rootvg" -o CuDv # Dependencies echo $0 " Deleting Dependencies " odmdelete -q "name = rootvg" -o CuDep odmdelete -q "dependency = rootvg" -o CuDep # Device Drivers echo $0 " Deleting Device Drivers " odmdelete -q "value1 = rootvg" -o CuDvDr odmdelete -q "value3 = rootvg" -o CuDvDr # Recover rootvg LVM info echo $0 " Recover rootvg LVM info " redefinevg -d $PV rootvg varyonvg -m1 rootvg echo $0 " shutting down followed by a reboot" shutdown -Fr ======================================================================== >(I)91194. Demo code available for new TCP/IP Products September 19, 1991 Prior to the general availability on the new TCP/IP products for DOS and OS2 on 10/25/91 the software may obtained using the following commands: For DOS: REQUEST TCPBETA FROM DOSTCPIP AT RALVMM -Entire package 3.5" REQUEST TCPBETA5 FROM DOSTCPIP AT RALVMM -Entire Package 5.0" REQUEST TCPBASE FROM DOSTCPIP AT RALVMM -Base kit 3.5" REQUEST TCPBASE5 FROM DOSTCPIP AT RALVMM -Base kit 5.0" REQUEST TCPNFS FROM DOSTCPIP AT RALVMM -NFS kit 3.5" REQUEST TCPNFS5 FROM DOSTCPIP AT RALVMM -NFS kit 5.0" REQUEST TCPPROG FROM DOSTCPIP AT RALVMM -Toolkit 3.5" REQUEST TCPPROG5 FROM DOSTCPIP AT RALVMM -Toolkit 5.0" Discussion of this package may be found on the DOSTCPIP FORUM on IBMPC. For OS2: REQUEST TCPBETA FROM OS2TCPIP AT RALVMM -Entire package REQUEST TCPDOC FROM OS2TCPIP AT RALVMM -Documentation REQUEST TCPBASE FROM OS2TCPIP AT RALVMM -Base Kit REQUEST TCPNFS FROM OS2TCPIP AT RALVMM -NFS Client/server REQUEST TCPPMX FROM OS2TCPIP AT RALVMM -X Windows kit REQUEST TCPX25 FROM OS2TCPIP AT RALVMM -X.25 REQUEST TCPPROG FROM OS2TCPIP AT RALVMM -Toolkit Discussion of this package may be found on the OS2TCPIP FORUM on IBMPC. After 10/25/91 the software will be available from PCPROD and OS2PROD for DOS TCP/IP and OS2 TCP/IP respectively. This code is distributed for IBM use. It may be used for customer demonstrations. No central support will be available until 10/25/91. Contact: Alan Reinhold (REINHOLD/RALYDPD) 8-352-2552 ======================================================================== >(I)91195. New AIX management functions called "ROSE" available (Our Austrian AIX freaks strike again:) Desription of the program ROSE for AIX 3 | The program ROSE (Remote Operating System Extensions) is an userinterface for the administration of an AIX 3 (UNIX) network. This product has a menudriven userinterface (like smit) and can be executed under monitor control by a user. The program ROSE keeps functions for administration and assistance (support) for distributed systems. For the administrator it is possible to handle distributed systems (LAN and WAN) on his place of work. The most important advantage of ROSE is the reduction of official journeys and the possibility of rapid help for every end-user: The functions are based on TCP/IP (rcp, rsh .....) and driven by C- and shellprograms. Brief summary: - menudriven or monitor-controlled - functions and text(module) are expansible easily by user (shell or C-programs) - NLS available - hierachical software-distribution - administration and support for enduser on remote-systems - administration of file systems on remote-systems - all commands can be executed on many AIX-UNIX hosts at the same time - installation of products with odm - receiving reports of actions - turning signed generator for running commands ROSE is a summary of functions produced by IBM AUSTRIA AIX TEAM and is available as a tool to be used as it is| For detailed information pls contact: Roman Szemeliker, 61814279 at VIEVMA ======================================================================== >(U)91196. Printing for Fun and Profit Under AIX V3 (GG24-3570) Now Available The new ITSC Redbook, Printing for Fun and Profit Under AIX V3 (GG24-3570), is now available from Mechanicsburg. The document is summarised below: An important function of modern computing environments is the capability to output information on paper, or print. This document focuses on the printing facilities available in AIX* V3 for the RISC System/6000* (5756-030). Many of these facilities are new or unique to AIX V3. This document is aimed at helping people, such as systems managers, systems engineers, or integrators to understand: - The manner in which AIX V3 print spooling subsystem functions - How to install printers - How to configure printers and the print spooling subsystem - How to print files and manage the progress of print requests through print spooling subsystem - More advanced printing topics such as remote printing, printing via terminals (IBM 3151), printing via Xstations and configuring nonsupported printers. Mark Johnson - ITSC Austin - MARKJOHN at AUSVM8 - 23 September 1991 ======================================================================== >(U)91197. Commandline Editing in the Korn Shell with Cursor Keys The Korn shell allows commandline editing with either vi or Emacs key codes. When using Emacs key codes there is also a possibility to get commandline editing with the curosr keys. Put the following in your .kshrc file (Or wherever $ENV points to): alias __A='' alias __B='' alias __C='' alias __D='' alias __H='' alias __P='' where __ is a ksh shortcut for ESC. the control codes have to be entered as real control codes not as When using vi, type

to get a CTRL-P in the text. and do not forget to set -o ignoreeof else the key might log you out (or don't define __P). (This tip originated in comp.unix.shell) ======================================================================== >(I)91198. Graphics bug in the GTO and 2007 PTF There is a bug in 3.1.5 where an application running on a 730 or GTO will be up to twice as slow the second time it is started. This is very noticeable on the demos - the 2nd time you start any graphics it seems to be running in mud. There is a fix in PTF 2007. Also a quick hint - 3D Windows will run VERY much slower if there is anythin g at all on top of them. Cheers Iain Elliot ======================================================================== >(U)91199. New AIX Family Catalog now in Mechanicsburg October 1, 1991 The 1991 edition of the AIX Family Catalog is now available in Mechanicsburg. This new catalog contains 2900 applications from 1350 software vendors. Applications are included for the entire family of AIX platforms: PS/2, RT, RISC System/6000, and S/370. You may obtain a copy of this catalog by ordering GC67-0210 from Mechanicsburg. For more information or questions about the AIX Catalog contact: Keith Tuffy, RHQVM21(TUFFY). ======================================================================== >(I)91200. XonDOS Corrective Service Fix There is a fix available through IBM Software Support for two problems experienced with the XonDOS program. Myself and others in my lab have tested the fix and it appears to correct at least two problems many users are complaining about, they are: 1) Eliminates 5 second interruptions in updating/displaying text within windows 2) Eliminates the need for the token-ring card to be set for interrupt level 3 The corrective service fix replaces the XonDOS TCPIP software provided. When contacting software support ask for the software fix for APAR #21230 or PMR #5x258. One thing to note. After installing the fix we had problems with FTP that caused the machine to lock up while transferring files. I talked with software support and a problem report is already open for this but a workaround is available that involves changing the maximum IP packet size on the RISC System 6000 (APAR #20029). It requires going into SMIT and changing the maximum IP packet size for the TR0 interface to 1024 (was previously 1500 on my machine). The following are the SMIT menu steps to change TR0 packet size: Communications Applications and Services TCP/IP Further Configuration Network Interfaces Network Interface Drivers Change/Show Characteristics of a Network Interface Driver select TR0 change Maximum IP Packet Size for THIS Device to 1024 press enter then PF10 to exit Hope this helps everybody as much as it did us. Chuck Hall Development Engineering, FSD Manassas ======================================================================== >(U)91201. OSIMF/6000 problem fix / missing DLC PROBLEM: -------- Trying to load osimf/6000 may fail with following message displayed: ***************************************************************** rc.osimf -ftam: Loading FTAM Wed Dec 12 16:40:17 CUT 1990 rc.osimf: Loading the OSI Stack and XTI Wed Dec 12 16:40:17 CUT 1990 Loading romd3rtr build SYS_CFGKMOD: Cannot create another process at this time. Can't load OSI stack rc.osimf: ERROR: /usr/lpp/osimf/etc/osi_ldr status=11 ****************************************************************** CAUSE: ------ There is no Data Link Control available for the adapter you are trying to use. SOLUTION: --------- Add a Data Link Control for the adapter: - smit devices - Communication Devices - XXXXXXX Adapter - Services - Data Link Controls - Add an XXXXXXX Data Link Control - dlc IEEE_ethernet dlc IEEE Ethernet (802.3) Data Link Control Miguel Crisanto, AIX FSC Munich ======================================================================== ======================================================================== Albert Einstein, when asked to describe radio, replied: "You see, wire telegraph is a kind of a very, very long cat. You pull his tail in New York and his head is meowing in Los Angeles. Do you understand this? And radio operates exactly the same way: you send signals here, they receive them there. The only difference is that there is no cat." >91.10.11 Table of contents: (U)91202. Subject: XGA Display Adapter/A and 8514 Display (I)91203. AIX SNAFLOW TRACE FORMATTER FOR RISC SYSTEM/6000 UPDATES AVAILABLE (I)91204. NEW 33MHZ RISC SYSTEM/6000 POWERSTATION/POWERSERVER (I)91205. UPDATED RISC SYSTEM/6000 PERFORMANCE ON HONE COMP AND PEC TOOLS (I)91206. INSTALLING AND USING WDSF/VM DOCUMENT AVAILABLE ON MKTTOOLS (U)91207. RISC SYSTEM/6000 MULTIPROCESSOR PRODUCT LINE DIRECTION (I)91208. HP OPENVIEW Q'S AND A'S NOW AVAILABLE ON TOOLS (U)91209. Migrating from Sun and DEC to IBM ======================================================================== >(U)91202. Subject: XGA Display Adapter/A and 8514 Display TITLE: DSSC FLASH 1176 AIX PS/2 XGA VIDEO SUBSYSTEM SUPPORT Dallas National Marketing and Technical Support Center Document Number F1176 10/09/91 AIX PS/2 XGA VIDEO SUBSYSTEM SUPPORT AIX PS/2 v1.2.1, with the application of PTF U401439, service level 1008 , contains support for the XGA video subsystem. The XGA subsystem offers highe r speed VGA and Extended Function 1024x768 graphics resolution. The XGA vide o subsystem is integrated directly on the system board in Model 90s and 95s, an d is available as an adapter card for other systems. The XGA co-processo r provides the following hardware drawing-assist functions: o Pixel-Block or Bit-Block Transfers o Line Drawing o Area Full o Logical and Arithmetic Mixing o Map Masking o Scissoring o X, Y Axis Addressing o Hardware Sprite (cursor) With the application of service level 1008, X-Windows also includes suppor t for the XGA video subsystem. The XGA X-Windows implementation support s 1024x768 resolution with 256 colors, and requires 1MB video memory. Al l available 1024x768 displays are supported. With the application of service level 1008, XGA support has been added for th e IBM PS/2 Models 90 and 95. XGA support will be added for the IBM PS/2 Model s 70 and 80 in a later service level. The card must be attached via a 32-bi t expansion slot. ======================================================================== >(I)91203. AIX SNAFLOW TRACE FORMATTER FOR RISC SYSTEM/6000 UPDATES AVAILABLE October 2, 1991 Updates to the AIX SNAflow Trace Formatter for the RISC System/6000 are available on the AIXIC Tools Disk. SNAflow decodes and formats SNA Services/6000 attachment traces for the RISC System/6000. The latest version (1.10) includes corrections and enhancements to the original release. To request the SNAflow package, enter the following from your VM/PROFS command line: TOOLS SENDTO DALVM41B TOOLS AIXIC GET SNAFLOW PACKAGE To subscribe to the SNAflow package so that you will receive updates as they are released, enter the following from your VM/PROFS command line: TOOLS SENDTO DALVM41B TOOLS AIXIC SUB SNAFLOW PACKAGE The SNAflow tool and associated documentation is considered IBM Internal Use Only. Questions on this notice may be referred to: AMINI at DALVM41B ======================================================================== >(I)91204. NEW 33MHZ RISC SYSTEM/6000 POWERSTATION/POWERSERVER October 2, 1991 Today IBM announces a new level of deskside price/performance for the RISC System/6000 product line. The new 33MHz POWERstation/POWERserver 530H yields 20 Mflops (Linpack DP) and a SPECmark of 57.4. These performance metrics represent a 32% over the POWERstation/POWERserver 530. Base models of the 530H come with 32MB RAM and 400MB of SCSI fixed disk storage. The base model price is $31,500--no increase from the 530. The 400MB disk drive gives users 13% more base storage with a faster seek time and transfer rate than the 530. Model conversions from the POWERstation/POWERserver 520 to the 530E (planar speed of the 530H) and 530H to the 550E (planar speed of the 550) are also available. Also, effective today, the POWERstation/POWERserver 530 and 540 and the POWERstation 730 are withdrawn from marketing. Information on backlog conversion of on-order POWERstation/POWERserver 530's and 540's to the new 530H can be found in the announcement letter 191-186. Foil masters suitable for internal and customer presentations covering this announcement are available electronically. To access the file, type the following command on your profs command line: TOOLCAT MKTTOOLS GET RS6K102 PACKAGE The file is a "TERSED" LIST3820 file. Therefore, before printing you will need to unpack it, using the following command: TERSE RS6K102 TERS3820 A1 RS6K102 LIST3820 A1 (UNPACK This procedure will give you a file named RS6K102 in LIST3820 format. The RISC System/6000 Facts & Features brochure (G320-9878) has been updated to include the POWERstation/POWERserver 530H. It will be available from Mechanicsburg on 10/21. A new spec sheet for POWERstations/POWERservers 500 series (G221-3223) has been created. It will be available for ordering in Mechanicsburg on 10/28. ======================================================================== >(I)91205. UPDATED RISC SYSTEM/6000 PERFORMANCE ON HONE COMP AND PEC TOOLS October 2, 1991 IBM Internal Use Only Performance and price performance information for the IBM RISC System/6000 530H is now available from the HONE COMP database and the PEC TOOLS disk. The following table summarizes the performance of the new RISC System/6000 530H and compares it to existing RISC System/6000 models. Please note that the performance for previous systems using these benchmarks is unchanged (the exception is the TPC benchmarks). Older RISC System/6000 models are listed so comparisons can be made to the new 530H. Benchmark(metric) 320 320H 520 530 530H 930 540 550 950 ----------------- ---- ----- ---- ---- ---- ---- ---- ---- ---- SPEC Release 1(geo mean) SPECmark 32.8 41.2 32.6 43.4 57.4 52.4 72.2 72.2 SPECint 15.9 20.0 15.8 20.1 26.6 24.4 33.9 33.8 SPECfp 53.1 66.8 52.9 72.5 95.9 87.3 119.7 119.7 SPEC SDM(peak throughput, scripts/hr) sdet 138.9 140.6 234.6 Linpack(MFLOPS) Single Prec. 10.5 13.3 10.5 14.4 19.2 14.5 17.3 24.3 24.3 Double Prec. 9.2 11.7 9.2 15.2 20.0 15.2 18.3 25.2 25.2 AIM APR II AIMs 16.4 20.7 16.9 21.3 27.9 20.8 24.9 34.5 34.6 Max User load 141 193 156 197 244 195 227 307 310 ************************************************************************ IMPORTANT INFORMATION ON TPC-A PERFORMANCE ************************************************************************ * The RISC System/6000 520 and 530H were measured using a new TPC-A application implementation which improved the efficiency of terminal I/O. This new implementation is similar to the way other vendors have implemented the TPC-A application and makes the RISC System/6000 results more comparable to competitive TPC-A UNIX performance claims. The performance improvements were due to these application changes with some additional systems tuning. Customers will not see this type of performance improvement in their applications unless they implemented terminal I/O in a similar manner. * The 530H TPC-A TPS is the same as the 550 due to terminal attachment constraints. The maximum number of terminals that can be attached to the 530H and 550 via ASYNC cards is 320 (5 64 port cards). Based on TPC-A rules, 320 terminals can generate a maximum of 32 TPS. Both the 530H and 550 could achieve a higher TPC-A TPS rating if more terminals could be attached. The Performance Evaluation Center is currently investigating methods which would allow attaching more terminals and increase the TPC-A TPS ratings for the 530H and 550. * Along with many other vendors, the RISC System/6000 TPC-A implementation used the INFORMIX relational data base product. INFORMIX announced a price increase effective 8/1/91 which is included in the RISC System/6000 price performance calculations. This price increase is NOT REFLECTED in many of the competitors' TPC-A or TPC-B results. * In COMPETITIVE SITUATIONS where TPC-A price performance is a factor, make sure that the competition is pricing their systems using current INFORMIX prices. * The following table summarizes IBM RS/6000 TPC-A and TPC-B performance and price performance results compared to representative competition. TPC-A COMPARISON System TPC-A K$/TPS K$/TPS TPS Old Informix Current Informix Pricing Pricing RISC System/6000 520 23.0* N/A 16.8 RISC System/6000 530H 32.0* N/A 16.2 RISC System/6000 550 32.0 14.8 16.1 RISC System/6000 950 38.0 21.8 23.8 HP 807S 20.8 16.7 17.4 (e) HP 827S 33.7 14.5 16.5 (e) HP 847S 42.8 14.6 15.5 (e) AT&T Starserver E 24.8 14.5 18.9 (e) Sequent S2000-200 49.9 14.9 15.8 (e) * The RISC System/6000 520 and 530H used an updated TPC-A implementation that is consistent with that used by HP, UNISYS and SEQUENT and approved by the TPC. The 530H, 550 and 950 will be measured again when a method to attach more terminals is available. TPC-B COMPARISON System TPC-B K$/TPS K$/TPS TPS Old Informix Current Informix Pricing Pricing RISC System/6000 320H 41.4 2.6 2.8 RISC System/6000 520 N/A N/A N/A RISC System/6000 530H 52.6 N/A 2.9 RISC System/6000 550 69.2 3.0 3.1 RISC System/6000 950 74.2 4.5 4.8 Data General AV 6240 102.9 4.2 4.2 AT&T Starserver E 45.0 2.9 3.1 (e) AT&T Starservr S 47.8 3.1 3.2 (e) Sun SPARCserver 2 39.7 2.6 2.7 (e) Sun SPARCserver 470 75.2 4.5 4.6 (e) (e): estimate based on new Informix pricing. The following documents on PEC TOOLS and HONE COMP have been UPDATED to reflect the 10/02/91 announcement and will be available immediately except where noted. This is not a complete list of all the documents on HONE COMP or PEC TOOLS. RISC System/6000 Performance on PEC TOOLS PEC Tools contains scripted presentations (with foil notes) such as RS6TPCAB and RS6CIP that may be shown to customers, official performance summary sheets for AIM (example AIMALL, AIM320H etc) and SPEC Release 1 (SPECALL), TPC Benchmark A and B Full Disclosure Reports etc. All PEC Tools documents may be printed on an IBM 3820 page printer. Package name(s) Description ----------------- ------------------------------------------------- AIMALL AIM results for all RISC System/6000 systems AIM530H AIM results for 530H @@ RS6TPCAB RISC System/6000 TPC A and B Performance VS Competiti on @@ TPC6FDA2 Updated RISC System/6000 TPC A Full Disclosure Report @@ TPC6FDB2 Updated RISC System/6000 TPC B Full Disclosure Report RS6CIP RS/6000 Compute Intensive Performance VS Competition - Linpack and SPEC Release 1 ## RS6KPB RISC System/6000 Performance Brief SPECALL RS/6000 SPEC Release 1 press release result sheets SPECRES Table of IBM & Competitive SPEC Release 1 results %% SDM10PRF RISC System/6000 SPEC SDM 1 Performance VS Competitio n %% SDM10ALL Press release sheets : RISC System/6000 SPEC SDM 1 @@ RS6TPCAB, TPC6FDA2 and TPC6FDB2 will be available on or before 10/4/91 ## RS6KPB will be withdrawn and updated at a later date %% Will be available on or before 10/11/91 How to access PEC performance data on PEC TOOLS To obtain a copy of a PEC TOOLS package, please issue the following command from your PROFS/CMS command line: TOOLS SENDTO DALVM41B TOOLS PEC GET PACKAGE using the actual package name (for example RS6CIP) instead of . To receive updates automatically, subscribe to these packages using the following command: TOOLS SENDTO DALVM41B TOOLS PEC SUB PACKAGE using the actual package name (for example RS6CIP) instead of . ALTERNATELY, you may use the TOOLCAT facility. Please see the 'PEC Performance Index' article on HONE COMP for detailed instructions on the Toolcat facility which makes it easier to access and subscribe to PEC TOOLS documents. RISC System/6000 Performance on HONE COMP HONE COMP contains descriptions of the benchmarks and performance ratings in tables for IBM and competitive systems as follows. Benchmark Document name ----------------------------- ---------------------------------- SPEC 1.0 UNIX Wkstn Perf. : SPEC Benchmarks Dhrystone 1.1, 2.1, MIPS, UNIX Wkstn Batch Comp. Int. Perf. Whetstone, Linpack, Livermore Loops and Khornerstone AIM UNIX System Perf. : AIM Benchmarks TPC - A and B TPC Benchmarks A and B Perf. Data How to access PEC performance data on HONE COMP: 1) Access and logon to HONE, 2) Type 'comp' and press enter on HONE main menu, 3) Type 'pec' in the category field in the COMP main menu and press enter, 4) Select the article by number. If there are any questions, please send a note to PEC at DALVM41B. ======================================================================== >(I)91206. INSTALLING AND USING WDSF/VM DOCUMENT AVAILABLE ON MKTTOOLS October 4, 1991 A document on installing and using the Workstation Data Save Facility/VM product is now available on MKTTOOLS. This document was written from the perspective of both the workstation end-user and the VM systems programmer. Topics include the end-user's view of WDSF, WDSF administration and host installation, other uses of WDSF and hints and tips. This information can be provided to customers. This document can be retrieved from MKTTOOLS by issuing the following command: tools sendto bcrvmms1 tools mkttools get seaswdsf package Note: the document on MKTTOOLS is in LIST3820 format and is tersed. Contact: UKFSCXA(WALMSLEY) ======================================================================== >(U)91207. RISC SYSTEM/6000 MULTIPROCESSOR PRODUCT LINE DIRECTION September 30 1991 With SUN's multiprocessor product line announcement (Oct 30th) customer inquiries to RISC System/6000 MP development are certain to increase. The following can assist you with these inquiries. It was provided by Phil Hester, AWD Engineering Center Director, as to the status of RISC System/6000 MP development: AWD remains committed to developing multiprocessor solutions addressing traditional, tightly-coupled, shared-memory MPs as well as loosely-coupled clusters of processors connected together over Ethernet/Token Ring as well as fiber optics and higher speed interconnection networks. The hardware and software required for these product offerings are all under development. AWD will strive to bring these products to market on the best possible schedule consistent with our other products priorities. Marketing Contact: AARTALE at RHQVM05 ======================================================================== >(I)91208. HP OPENVIEW Q'S AND A'S NOW AVAILABLE ON TOOLS October 8, 1991 The September 17, 1991 Open Software Foundation (OSF) Distributed Management Environment (DME) technology selection announcement has renewed interest in the IBM licensing announcement made for portions of Hewlett-Packard Company's OpenView network management software. There were 57 questions and answers prepared for the the April 16, 1991 announcement which are now available on TOOLS. To pull the package from MKTTOOLS, type the following on your PROFS/VM command line: TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET CSOPENVW PACKAGE Contact: Jon Thew, Client/Server Marketing, RHQVM04(JONTHEW) ======================================================================== >(U)91209. Migrating from Sun and DEC to IBM There are some new migration guides available: GG22-9494-00 SUN TO RISC SYSTEM/6000 MIGRATION GUIDE GG22-9495-00 DEC VAX/VMS 5.4 TO RISC/6000 AIX VERSION 3.1 MIGRATION GUIDE ======================================================================== ======================================================================== A transistor protected by a fast-acting fuse will protect the fuse by blowing first. >91.10.18 Table of contents: (U)91210. Mounting a floppy filesystem on a /6000 (I)91211. SCSI problems with odd tape block size (I)91212. AADU Security problems and Update 2006 (U)91213. How to make an Exabyte tape work on a /6000 ======================================================================== >(U)91210. Mounting a floppy filesystem on a /6000 Unfortunately just readonly, but better than nothing| This is how to mount a filesys onto diskette : 1) # mkdir diskt (create a directory to hold all the files that will be mounted onto the diskette) 2) create files in "diskt" directory. 3) # proto diskt > proto_diskt (create a prototype file that contains infor about the "diskt" directory) 4) edit proto_diskt to insert 0 0 at the first line of proto_diskt. 5) insert a formatted diskette into diskette drive 6) # mkfs -p proto_diskt -Vjfs /dev/fd0 (create filesys in diskette) 7) # mount -r -Vjfs /dev/fd0 desire_mount_point (mount the diskette filesys) 8) # umount /dev/fd0 (to unmount the filesys) Note : it's only a read-only filesys : unmount the filesys before sys backup. Regards. Chiam YS Technical Services Operations, Malaysia. ======================================================================== >(I)91211. SCSI problems with odd tape block size RISC SYSTEM/6000 CONFIGURATION EXPOSURE BRANCH OFFICE INSTRUCTIONS MARKETING ACTION REQUIRED The following instructions are for your use in notifying your customer(s) of a potential problem with certain configurations of the RISC SYSTEM/6000. Marketing Representatives must notify affected customers of this exposure within 10 days and assist them in taking the appropriate action for their specific situation. The affected configurations are as follows: All RISC SYSTEM/6000 models with SCSI I/O controllers using tape devices. Normal marketing procedures concerning notification of customers will be followed. Each Marketing branch will keep accurate records indicating that each affected customer was notified of the exposures. Records must include (1) model and serial number of the system, (2) customer number, (3) customer name, (4) name of person contacted, (5) date of contact, and (6) name of IBM Marketing Representative who made the contact. IBM Marketing Representatives must also contact any customer who is in possession of a loaner machine with the above configuration. In addition, Industry Remarketers must be instructed to notify all their customers who purchased systems of this configuration and confirm to IBM in writing when they have completed notifying their customers. This package consists of the following sections: 1. Problem definition for use with customers. 2. Instructions for problem prevention. 3. Prepared Q's and A's. 4. Problem determination flow chart. _______________________________________________________________________ 1. Problem definition for use with customers. When the SCSI I/O controller is doing a READ from tape that has variable length records or fixed block records whose size is not divisible by 4, there is a possibility that the data can be corrupted. This problem occurs when doing a SCSI READ, not on a WRITE operation. Therefore all data written to a device is not corrupted regardless of the transfer option used. The problem will occur only if all the following conditions are met: - The size of the variable block to be read from the tape is not a multiple of 4. - The tape write/read operation must be performed by other than the AIX utilities "tar", "cpio", or "restore". - The block size for the tape read operation is different than that of the actual size of the block to be read IBM will be shipping the fix for this problem to all customers. It is highly recommended that all customers install the fix. _______________________________________________________________________ 2. Instructions for problem prevention. The micro code on one of the SCSI Controller chips must be updated from diskette. In the interim, customers should set their tape drives to a fixed block size that is evenly divisible by 4 (eg. 512). If previously written tapes do not comply with this condition, the reading of such tapes should be delayed until the fix is installed. Correction of the SCSI I/O controller problem is a very high priority item and will be quickly resolved. IBM will provide an update diskette as soon as the code fix has completed testing. This problem will be resolved in an Engineering Change Announcement (ECA). Target distribution for this ECA is late 4Q 91. Since this repair is accomplished via an EC, it is important that AAS reflects accurate customer and Service B/O information as appropriate. _______________________________________________________________________ 3. Prepared Q's and A's Please note that the following Q's and A's are not to be distributed to the customers. Q1 What exactly is the problem? A1 When data is READ from a SCSI tape device using variable length blocks or fixed length blocks that end on a non 4 BYTE boundary data corruption can occur.The condition will not occur with records that end on any 4 BYTE boundary (eg. multiples of 512). Q2 What causes the problem? A2 A design error in a chip that is located on the SCSI I/O controller. This will be corrected by a micro code change from diskette. Q3 What effect will this have on my data? A3 Errors can potentially be introduced. During a READ operation, several BYTES of data may be corrupted in blocks that are not multiples of 4 BYTES long. There will be no warning from the system that data has been corrupted. Q4 Is the data on my tape good? A4 Yes. The data has been written correctly. Only on a READ from tape will a possible corruption occur. Q5 What can I do to avoid this problem? A5 Use default block sizes when writing or reading to SCSI devices (eg. 512 BYTE). When using variable length records,specify only boundaries that are multiples of 4. The problem may also be avoided by using the standard AIX utilities cpio, tar, and backup/restore to write and read tapes. The dd utility may also be used if bs, ibs, and/or obs flags are set to a value evenly divisible by 4. Q6 What is the solution to the problem? A6 The solution will require new micro code be down loaded to the SCSI controller. This will be accomplished via a diskette that will be sent to all customers. Q7 How is IBM notifying its customers with the affected configurations? A7 IBM Marketing Representatives and Business Partners will make arrangements to contact each customer individually. Q8 Has IBM stopped shipment of these products? A8 We are not stopping shipment. The problem has been identified and has a working solution, to be implemented in new ships in the near term. A notification of the problem will be added to the new ships until a permanent fix is in place. Q9 What does this say about the reliability of IBM computer systems? A9 This problem relates to only SCSI I/O controller board assemblies. IBM is committed to providing its customers with the most advanced and reliable computer systems. As with all technology, problems can arise. We attempt to minimize those situations and deal effectively with those that occur. Q10 How did IBM become aware of this problem? A10 This problem was discovered and verified in an IBM laboratory. Q11 Does this problem exist on other IBM systems? A11 This problem is known only on the RISC SYSTEM/6000. Q12 What are IBM's plans to fix my system? A12 As quickly as the testing has been completed, diskettes will be shipped to all customers along with instructions on how to apply the fix. If required, the customer may request an early version of the fix that is being tested. This diskette is requested through your hardware support structure; refer to ECA number 039. It must be made clear that the early version fix is the same code fix version now being tested and therefore no guarantees can be made that there won't be another level. Q13 Doesn't IBM test their systems sufficiently to prevent this type of problem? A13 We are evaluating our development and test process due to this problem. As with all technology, problems can arise. We attempt to minimize those situations and deal effectively with those that occur. _______________________________________________________________________ 4. Problem determination flow chart. The following is provided as an alternative method for an end-user to determine if he may have a problem in reading SCSI tapes: Assume RS/6000 with SCSI tape drive and one of the affected SCSI Adapters. 1. Have you ever varied your tape drive's block size setting (usually via SMIT) to a number of bytes not evenly divisible by 4 or to a variable block size? A. Yes (GOTO 3) B. No (GOTO 2) 2. Do you ever read tapes from another system that uses a block size not evenly divisible by 4 or variable block size? A. Yes (GOTO 3) B. No (TERMINATE - No Problem) 3. Do you use ONLY AIX utilities OTHER than dd to read tapes (i.e., tar, cpio, backup/restore)? A. Yes (TERMINATE - No Problem) B. No (GOTO 4) 4. Do you write programs to read from tape (i.e., use the read() function call)? A. Yes (GOTO 6) B. No (GOTO 5) 5. Do you use the dd utility to read tapes with block sizes that are not evenly divisible by 4 or are of variable length? A. Yes (GOTO 6) B. No (TERMINATE - No Problem) 6. You are at risk of having tapes that cannot be read correctly until the SCSI micro code update is installed on your system. The only tapes that could be read with errors are those whose variable or fixed byte blocks do not end on a 4-byte boundary in memory. Any tapes written with fixed byte blocks that end on a 4-byte boundary, or with any of the AIX utilities that control block sizes (eg. tar, cpio, backup/restore) are not at risk and can be read prior to installation of the fix. ======================================================================== >(I)91212. AADU Security problems and Update 2006 RISC SYSTEM/6000 CONFIGURATION EXPOSURE BRANCH OFFICE INSTRUCTIONS MARKETING ACTION REQUIRED The following instructions are for your use in notifying your customer(s) of a problem with a software application running on the RISC SYSTEM/ 6000 for DOS-based personal computers or PS/2 running AADU. Marketing Representatives must notify affected customers of this exposure within 10 days and assist them in taking the appropriate action for their specific situation. The affected configurations are as follows: All RISC SYSTEM/6000 models that are using the DOS Server feature and operating under AIX level 3005 with PTF 2006 installed. The systems that can connect are any DOS-based personal computer or PS/2 running AADU (AIX Access for DOS Users). Normal marketing procedures concerning notification of customers will be followed. Each Marketing branch will keep accurate records indicating that each affected customer was notified of the exposures. Records must include (1) model and serial number of the system, (2) customer number, (3) customer name, (4) name of person contacted, (5) date of contact, and (6) name of IBM Marketing Representative who made the contact. In addition, Industry Remarketers must be instructed to notify all their customers who are using this application and confirm to IBM in writing when they have completed notifying their customers. This package consists of the following sections: 1. Problem definition for use with customers. 2. Instructions for problem prevention. 3. Prepared Q's and A's. _______________________________________________________________________ 1. Problem definition for use with customers. Any user who logs onto the RISC SYSTEM/6000 using AADU that is operating under AIX version 3.1 level 3005 with PTF 2006 installed will be granted super user (root) authority on that system regardless of the user's ID. This will result in a compromise of the system security. _______________________________________________________________________ 2. Instructions for problem prevention. Systems that are not at PTF level 2006 do not have this problem. Systems that are, and are concerned that the authorized users may access sensitive data, may wish to wait until PTF 2007 and revoke access to those users in the mean time. Another alternative is to request the available emergency fix. It must be noted that although this emergency fix has been tested individually, the fix code is still being imbedded in the next level PTF (2007) which is still in regression test. _______________________________________________________________________ 3. Prepared Q's and A's Please note that the following Q's and A's are not to be distributed to the customers. Q1 What exactly is the problem? A1 When an AADU user logs onto the system that users access privileges are automatically set to that of root for the entire session. Q2 What caused the problem? A2 The problem was created when a defect in a related area was being corrected in the AIX DOS server code. In order to correct the initial problem the user authority needed to be set to SU levels. A subsequent re-setting to default authority was to occur after the user established a session. This re-setting portion contained a code defect. Q3 What effect will this have on my systems security? A3 Each system is exposed to having the entire file system accessible to all users that log into the system using AADU. Therefore the security of all data is non existent. Q4 What is the solution to the problem? A4 The fix for the DOS server problem is contained in PTF 2007. Q5 How is IBM notifying its customers with the affected configurations? A5 IBM Marketing Representatives and Business Partners will make arrangements to contact each customer individually. Q6 Has IBM stopped shipment of these products? A6 We are not stopping shipment. The problem has been identified and has a working solution. This will be implemented in new ships in the near term. Q7 How did IBM become aware of this problem? A7 This problem was discovered by an IBM customer and verified in our laboratory. Q8 Does this problem exist on other IBM systems? A8 This problem is known only on the RISC SYSTEM/6000 Q9 What are IBM's plans to fix my system? A9 A planned PTF (2007) is scheduled for availability during the 4th quarter 91. This PTF will resolve this problem. As an alternative an emergency fix may be installed. If an emergency fix is to be requested , refer to APAR IX19112 when discussing the request with level 2 support. Q10 Doesn't IBM test their systems sufficiently to prevent this type of problem? A10 We are evaluating our test process due to this problem. As with all technology, problems can arise. We attempt to minimize those situations and deal effectively with those that occur. ======================================================================== >(U)91213. How to make an Exabyte tape work on a /6000 We didn't test it so far but if it works it would be great. afx From: Frank Kraemer Sub: Get a EXABYTE (8200) tape to work (plus others.....) Info: A customer told us that after he had changed one item in the ODM database he could use the EXABYTE tape without a need for additional device drivers. ************************************************************* This are some of the contents in the file /etc/objrepos/PdAt on AIX level 3005. PdAt: uniquetype = "tape/scsi/8mm" attribute = "mode" deflt = "yes" values = "yes,no" width = "" type = "R" generic = "DU" rep = "sl" nls_index = 2 PdAt: uniquetype = "tape/scsi/8mm" attribute = "block_size" deflt = "1024" values = "0-245760,1" width = "" type = "R" generic = "DU" rep = "nr" nls_index = 3 PdAt: uniquetype = "tape/scsi/8mm" attribute = "extfm" deflt = "no" values = "yes,no" width = "" type = "R" generic = "DU" rep = "sl" nls_index = 4 PdAt: uniquetype = "tape/scsi/8mm" attribute = "ret" deflt = "no" values = "no" width = "" type = "R" generic = "" rep = "sl" nls_index = 0 PdAt: uniquetype = "tape/scsi/8mm" attribute = "dev_type" deflt = "1" values = "1" width = "" type = "R" generic = "" rep = "n" nls_index = 0 PdAt: uniquetype = "tape/scsi/8mm" attribute = "model_name" deflt = "EXB-8200 " values = "" width = "" type = "R" generic = "" rep = "s" nls_index = 0 PdAt: uniquetype = "tape/scsi/8mm" attribute = "min_read_error" deflt = "6" values = "6" width = "" type = "R" generic = "" rep = "nr" nls_index = 0 PdAt: uniquetype = "tape/scsi/8mm" attribute = "min_write_error" deflt = "6" values = "6" width = "" type = "R" generic = "" rep = "nr" nls_index = 0 PdAt: uniquetype = "tape/scsi/8mm" attribute = "read_ratio" deflt = "200" values = "200" width = "" type = "R" generic = "" rep = "nr" nls_index = 0 PdAt: uniquetype = "tape/scsi/8mm" attribute = "write_ratio" deflt = "100" values = "100" width = "" type = "R" generic = "" rep = "nr" nls_index = 0 PdAt: uniquetype = "tape/scsi/8mm" attribute = "mode_data" >>>> deflt = "0x00001008000000000000040000048e028000020aa0a000000000000000 00" values = "" width = "" type = "R" generic = "" rep = "s" nls_index = 0 ************************************************************* The customer has changed one entry and his EXABYTE 8200 ran fine without an error. PdAt: uniquetype = "tape/scsi/8mm" attribute = "mode_data" >>>> deflt = "0x000010080000000000000200" values = "" width = "" type = "R" generic = "" rep = "s" nls_index = 0 Sorry but I was not able to check this, because we do not have such a tape (we do not have an 8mm at all...). Please provide some feedback. Howto change ODM : * use root * cd /etc/objrepos * save the file(s) PdAt to /tmp/PdAt.3005 * use ODME or * odmget PdAt > /tmp/PdAt.plain * edit PdAt.plain and delete all stanzas except these of: uniquetype="tape/scsi/8mm" and make the above changes * odmdelete "uniquetype='tape/scsi/8mm'" PdAt * odmadd /tmp/PdAt.plain * check with odmget command the PtAd ======================================================================== ======================================================================== A new direction for IBM: SDQ - Schedule Driven Quality (then the direction is closer to reality as MDQ) :-) >91.11.06 Table of contents: (U)91214. ARTIC AIX SUPPORT ANNOUNCED (U)91215. Shutdown without 'root' authorization (U)91216. IBM/Apple Enterprise Networking Guide for SNA Networks Available (U)91217. Redbook: Experiences in Using AIX NetView Service Point (U)91218. Redbook: Predicting Execution Time on the IBM RISC System/6000 (I)91219. AIX SNAFLOW TRACE FORMATTER FOR RISC SYSTEM/6000 UPDATES AVAILABLE (I)91220. Availability of SoftCopy Red Books on HONE (U)91221. 8TH EDITION OF MICRO CHANNEL ADAPTER CATALOG JUST RELEASED (I)91222. CAD EXPERT 1.6 NOW AVAILABLE| (I)91223. TCPPERF PACKAGE VERSION 1.2 UPDATED ON MKTTOOLS (U)91224. Timzones (I)91225. SPEC SDM 1 Performance (I)91226. FLOATING POINT ERROR HANDLER AVAILABLE FOR AIX V3.1 (I)91227. Getting PRPQS seems to be easier now (U)91228. Limit to the number of open windows on an Xstation (U)91229. VM minidisk mounted to System/6000 and the visible password (U)91230. SBus Token-Ring card now available for Sun machines (U)91231. A TFTP security warning from CERT (U)91232. Dualsession support for the 3151 (I)91233. Interface Builder for AIX (I)91234. Subset of the 2008 Update for the GTO and GL (U)91235. OEM rewriteable optical disks for the /6000 ======================================================================== >(U)91214. ARTIC AIX SUPPORT ANNOUNCED October 22, 1991 On OCT 22, 1991 IBM announced Realtime Interface Co-Processor AIX Support for RISC SYSTEM/6000. (ARTIC AIX Support, Program Number 5696-038) This product consists of a set of program services providing an interface between AIX processes and tasks running on IBM Realtime Interface Co-Processors installed on the RISC System/6000. ARTIC AIX Support provides RISC System/6000 customers with the capability to extend the communications capability of the RISC System/6000 by taking advantage of outboard communications processing on the ARTIC card. Outboard communications allows the RISC System/6000 to talk to devices and systems that require a variety of communication protocols not supported by standard hardware and software. Outboard communications also can be used to offload communications from the RISC System/6000 processor thus providing significant improvements in overall system performance. For additional information refer to the ARTIC AIX announcement letter #291-621. Please note that only certain configurations of ARTIC are specified in the announcement letter. Questions relating to support of additional ARTIC configurations or other aspects of this announcement should be sent to PROFS ID (BCRVM7(ARTICAIX). Additional questions may be addressed to Keith Laytham at VNET ID (BCRVMMS1(KEITH) or tieline 443-9861. ======================================================================== >(U)91215. Shutdown without 'root' authorization Normally 'root' or 'superuser' authorization will be required in order to run the shutdown command. If system administrator (root) does NOT want to execute 'shutdown' himself and does NOT want to pass root's password to anybody else but wants to allow 'normal' users to shutdown their box on their own, here's what to do: 1. Login as 'root'. 2. Create a 'dummy' user 'shutdown' via smit. 3. Select 'Change/Show Characteristics of a User' via smit and set 'ADMINISTRATIVE user' to true, set 'PRIMARY group' to 'system', set 'group set' to 'system'. 4. Edit file '/etc/passwd' and change the entry for 'shutdown' user to 'shutdown:!:0:0::/u/shutdown:/etc/shutdown -F' (normally you will just have to reset the first number to zero and change the end of the line to shutdown command). 5. Assign a new password for user 'shutdown'. 6. Pass password assigned in step 5 confidentially to the user(s) allowed to shutdown the box. After doing this, logging in as 'shutdown' will bring down the machine immediately. Many Thanks to Thomas Ludwig (BOE LAB) for this hint. Stefan Heilmann, Lab Boeblingen ======================================================================== >(U)91216. IBM/Apple Enterprise Networking Guide for SNA Networks Available IBM and Apple announced a series of agreements on 10/2/91, including an initiative concerning Enterprise Networking. Information on this initiative can be found in an earlier NETWORK bulletin board entry. The Enterprise Networking initiative focuses on the integration of Apple Macintoshes into IBM networks, both local area networks and wide area networks. A guide is now available to provide information to be used in supporting IBM and Apple networking requirements. This document describes the configurations that were verified during an interoperability study conducted by IBM and Apple at the IBM Multivender Network Facility in Research Triangle Park, NC, during September 1991. This document can be found on MKTTOOLS. The package name is APPLEIBM. Use the command: TOOLCAT MKTTOOLS GET APPLEIBM PACKAGE or your local procedure (e.g. OMNIDISK). This document includes path descriptions, lists of hardware and software used, configuring and operating procedures, configuration diagrams, and observations made during the study. Due to it's size (over 300 pages), please ensure you read the PACKAGE file and have enough storage to retrieve and print. It is intended for use with customers and is not classified or restricted. Thank You, Gino ======================================================================== >(U)91217. Redbook: Experiences in Using AIX NetView Service Point GG24-3700-00 Experiences in Using AIX NetView Service Point This publication describes uses of AIX NetView Service Point, Version 1. It provides basic examples of implementing AIX NetView Service Point on a RISC System/6000. This document is intended for people who need information related to the marketing and acceptance of the IBM RISC System/6000 AIX systems in a communications environment. A general knowledge of overall IBM and customer computing systems is assumed. This edition applies to Version 1 of the AIX NetView Service Point licensed program (Program Number 5621-107) which runs under Version 3.1 of the AIX operating system and NetView (Program Number 5665-362) for use with the MVS/ESA operating system. (234 pages) ======================================================================== >(U)91218. Redbook: Predicting Execution Time on the IBM RISC System/6000 GG24-3711-00 Predicting Execution Time on the IBM RISC System/6000 This report provides basic data from which a person can predict the execution time of a sequence of instructions on the RISC System/6000 family of computers. It provides the processor time for each non-privileged instruction, and describes many of the delays that occur between instructions due to data dependencies and branching. The emphasis is on timing short loops that are either fixed-point or floating-point bound. (50 pages) ======================================================================== >(I)91219. AIX SNAFLOW TRACE FORMATTER FOR RISC SYSTEM/6000 UPDATES AVAILABLE October 2, 1991 Updates to the AIX SNAflow Trace Formatter for the RISC System/6000 are available on the AIXIC Tools Disk. SNAflow decodes and formats SNA Services/6000 attachment traces for the RISC System/6000. The latest version (1.10) includes corrections and enhancements to the original release. To request the SNAflow package, enter the following from your PROFS command line: TOOLS SENDTO DALVM41B TOOLS AIXIC GET SNAFLOW PACKAGE To subscribe to the SNAflow package so that you will receive updates as they are released, enter the following from your PROFS command line: TOOLS SENDTO DALVM41B TOOLS AIXIC SUB SNAFLOW PACKAGE The SNAflow tool and associated documentation is considered IBM Internal Use Only. ======================================================================== >(I)91220. Availability of SoftCopy Red Books on HONE As you probably already know, the ITSO Red Books are now available as SoftCopy in BookManager READ/VM 1.2 format on the HONE systems and are accessible by everyone without special authorization. There are currently 230 different Red Books on-line and viewable with BookManager. All new Red Books will also be available in this format on-line. Major advantages of this SoftCopy library: o Improvement of timeliness of new and revised publications through electronic availability. o Improvement of effectiveness by users by eliminating outdated and obsolete information. o Increase productivity of information retrieval. o The use of the SoftCopy Library will yield a significant saving of pap e o The end-user is offered the possibility to retrieve or print a single chapter or paragraph instead of the entire document. Systems already operational are EHONE, ITHONE and APGHONE. A user can access the SoftCopy Library in several ways: o In the menu system by typing the fastpath name 'BOOKS' (in APGHONE: 'SCL') on the command line or by choosing option 'BOOKS' on the SUPPOR T menu. o In CMS by typing 'SCL' on the command line. Further systems will go operational with BookManager READ/VM 1.2. For the exact timetable on the system, which serves you, you might inquire via you r MISC Manager or your country HONE coordinator. We understand, that a numb e of SEs do also have access to the central HONE systems and therewith acces s to the SoftCopy Library. Please be aware of this new facility and communicate it to the field and t o all the Technical Support Groups interested. HONE will monitor for us the usage of this SoftCopy library. The following AIX specific redbooks are available on EHONE: GG243700 AIX NetView SP ZZ810296 AIX/ESA Overview GG243622 Elements of AIX Security: R3.1 GG243629 Writing a Device Driver for AIX Version 3 GG243735 CT/6000 versus CT/DOS GG243570 Printing Under AIX V3 GG243633 RISC System/6000 as Real-Time System GG243589 AIX 3.1 National Language Support GG243376 TCP/IP Tutorial and Technical Overview GG243676 Mainframe and Workstation NIC Software Compati... GG243458 X.25 Guide GG243692 AIX/V3 X.25 Communications GG243750 AIX Additional Authorization GG243695 Xstations GG243520 APPC and CPI-C Implementations GG243611 IBM RISC System/6000 NIC Tuning GG243649 Telecomms Products GG243178 LAN Concepts GG243727 Client/Server DB GG243696 Managing TCP/IP Networks GG243694 WDSF/VM GG243086 IBM Enhanced Connectivity Facilities SRPI Guide GG243711 RISC System/6000 Execution Times GG243507 SCSI - Architecture and Implementation ================================================================== >(U)91221. 8TH EDITION OF MICRO CHANNEL ADAPTER CATALOG JUST RELEASED November 4, 1991 The 8th edition of the CATALOG OF INTERNATIONAL MICRO CHANNEL EXPANSION ADAPTERS published by IBM is being released into Mechanicsburg as IBM Form #G360-2824-07. Information about expansion adapters from IBM as well as Independent Option Vendors (IOVs) from 22 countries that support the IBM* Micro Channel* architecture-based systems -- PS/2* computers, RISC System/6000* POWERstations and POWERservers and Micro Channel* 370 models. The expansion adapters are presented in 2 parts, those from IBM and those from IOVs, and each expansion adapter is listed alphabetically under the category heading that best describes its function. The information on each of the 1,020 expansion adapters included in this edition has been certified as accurate and up to date by an authorized representative of the IOV prior to be being included in this edition. Submitted adapter certifications and enrollments received after the published deadline are included in a separate Chapter, Chapter 4, where they are simply listed alphabetically by IOV without regard to category. Part 3 on pages 175-181 presents information and phone numbers to assist potential developers of expansion adapters around the world in obtaining the necessary documentation and assistance to support the Micro Channel architecture-based systems from IBM. *Trademark of the IBM Corporation. Questions on this notice may be forwarded to BCRVM5(MILI). ======================================================================== >(I)91222. CAD EXPERT 1.6 NOW AVAILABLE| November 5, 1991 New with CAD Expert 1.6: o IBM World Trade feature| The Sample CAD/CAM configurations and Price Lists are now ASCII files that users may modify outside CAD Expert with national pricing info. o Numerical Control machine tool concepts o The CADENCE, VALID and VIEWLOGIC product line for electronic design o CAMkit/6000 for enhanced Professional CADAM NC program generation o Updated prices for the RISC System/6000 disks o IBMcad version 3 -a new benchmark for PC-based CAD| CAD Expert assists (...over 700) Customers, SEs and MRs in selecting RISC System/6000 CAD/CAM solutions from IBM. It includes all the essential hardware and software information available in HONE on the subject on one 1.44MB diskette. CAD Expert runs on PS/2 DOS hypertext technology, a way of organizing information that lets one display only the information needed, in the order needed. To receive an electronic copy of CAD Expert, at the PROFS prompt enter TOOLS SENDTO DALNESSC TOOLS CADINFO GET CADXPRT PACKAGE To automatically receive CAD Expert updates, at the PROFS prompt enter TOOLS SENDTO DALNESSC TOOLS CADINFO SUBSCRIBE CADXPRT PACKAGE Please, address questions on PROFS to Sandy Albu at LSAVMIC1(SMALBU) ======================================================================== >(I)91223. TCPPERF PACKAGE VERSION 1.2 UPDATED ON MKTTOOLS November 5, 1991 This package has now been updated to include a copy of the recent 1991 Networking Systems Specialist Update presentation: IBM TCP/IP Performance Benchmarks, Session MVN119 This report compliments information previously available via this PACKAGE regarding the performance of MVS and VM TCP/IP when operating in Token Ring and Ethernet LAN environments and incorporates newly available information relating to: - the IBM 3172 model 2 and FDDI LAN environments; and - the MVS and VM TCP/IP TELNET servers. The TCPPERF PACKAGE may be requested from MKTTOOLS via the OMNIDISK facility. CONTACT: Robert Morse, 301-240-9963 (T/L 372) VNET: RDMORSE at WSCVM or TCPPERF at WSCVM Internet: rdmorsewscvm.vnet.ibm.com ======================================================================== >(U)91224. Timzones The TZ environment variable still seems to be a mistery for those that do no t follow US daylight savings time rules. Check out the documentation for /etc/environment for a thorough description of it. In Germany the correct TZ value should be: TZ=MEZ-1MSZ,M3.5,M9.5 Which would set the timezone to one hour east of GMT. Unfortunately AIX currently has a bug in evaluating it. A workaround for 1991 is TZ=MEZ-1MSZ,J90,J244 Here the switching dates are given by exact Julian dates while in the proper version one would select the month and the week. Henning Klages ======================================================================== >(I)91225. SPEC SDM 1 Performance The SPEC SDM Release 1 (Software Development Workload from SPEC) data for the RS/6000 530H has been incorporated in the following packages on the PEC TOOLS disk. SDM10PRF PACKAGE : Presentation with notes (script) containing a description of the benchmarks, IBM and competitive data and how to respond to competitive situations SDM10RES PACKAGE : Table of all SPEC SDM 1 results for IBM and competition available todate in a quick reference summary form SDM10ALL PACKAGE : RS/6000 SPEC SDM 1 results summary page (one per system) in the same format as published in the SPEC Newsletter. Robert Ryan, ITSC Austin 18 October 1991 ======================================================================== >(I)91226. FLOATING POINT ERROR HANDLER AVAILABLE FOR AIX V3.1 On the AIXTOOLS disk is a package which for use with XL Fortran Version 2 which enables the user to trap, report, and modify the results of floating point exceptions. This package, AIXFPE, includes C language source code for user routines to support OEM FPE features, the source code for the handler itself, and a test Fortran program with makefile for ensuring proper operation of the handler. Documentation is included in the package. Questions on this notice are to be forwarded to: DALVM41B(BRYANS) ======================================================================== >(I)91227. Getting PRPQS seems to be easier now I'm a member of the PRPQ development mission for AIX V3. For those of you who don't know what a PRPQ is, it is a Programming Request for Price Quotation. What these entail are customer requests for function which are small in development effort, and which improve the marketability of the system. PRPQs must be justifiable on a cost/charge basis. In other words, the costs associated with producing the PRPQ must be recouped in the price of the PRPQ (which is based on the volumes projected). PRPQs are now fully supported. At one time PRPQs were provided on an asis basis. My organization is interested in hearing from the field what functions they would like to see implemented as PRPQs. While this is not a commitment to actually provide the function we would like to have as input in order to determine priority. If you have any suggestions/comments please contact myself (SABADE at AUSTIN) or Janie White (JMWHITE at AUSVMQ) and we will determine if your idea merits submission of a request through Special Products Marketing. If there is sufficient interest we will create a PRPQ forum for these discussions. Thanks Steven Bade PSP PRPQ Development Austin SABADE at AUSTIN T/L 678-8207 ======================================================================== >(U)91228. Limit to the number of open windows on an Xstation There is a limit to the number of open windows...... Reference: RISC System Technology Guide - pg 121 - (SA23-2619) The 512K of DRAM associated with the 80186 (X120) - non expandable - can support up to 64 windows or sessions simultaneously. X130 is the same. Don Ferndelli It actually does not limit the number of windows, but the number of connected programs (sockets). afx ======================================================================== >(U)91229. VM minidisk mounted to System/6000 and the visible password When mounting a VM minidisk then the password must be given on the commandlin e and is later visible with the mount command. Not very secure indeed. Here is a solution: Use the mountpw command to send the password to VM separately, before the mount command is executed. -Richard Ryniker ======================================================================== >(U)91230. SBus Token-Ring card now available for Sun machines I received an informational letter from Aurora Technologies advertising their new TR card. Some details: -- 4-Mbit -- Works on SPARCStation 1, 1+, 2, IPC, and IPX running Sun OS 4.1 or above -- Card with TCP/IP support: $895 -- Packages to support SNA (3270, 3770, and LU0) at $1950 each Aurora's numbers: Phone: (617) 290-4800 FAX: (617) 290-4844 Address: 176 Second Avenue Waltham, MA 02154 Scott Friedman ======================================================================== >(U)91231. A TFTP security warning from CERT The Computer Emergency Response Team/Coordination Center (CERT/CC) has received information concerning a vulnerability in the TFTP daemon in all versions of AIX for IBM RISC System/6000 machines. IBM is aware of this problem and a fix is available as apar number "ix22628" . This patch is available for all AIX releases from "GOLD" to the current release. NOTE: THIS IS AN UPDATED PATCH FROM ONE RECENTLY MADE AVAILABLE and fixes a security hole in the original patch. The SCCS id of the correct patch is tftpd.c 1.13.1.3 (*not* 1.13.1.2 or earlier versions). This can be checked using the following "what" command. % what /etc/tftpd /etc/tftpd: 56 1.13.1.3 tftpd.c, tcpip, tcpip312 10/10/91 09:01:48 tftpsubs.c 1.2 com/sockcmd/tftpd,3.1.2,9048312 10/8/89 17:40:55 IBM customers may call IBM Support (800-237-5511) and ask that the fix be shipped to them. The fix will appear in the upcoming 2009 update and the next release of AIX. --------------------------------------------------------------------------- I. Description Previous versions of tftpd did not provide a method for restricting TFTP access. II. Impact If TFTP is enabled at your site, anyone on the Internet can retrieve copies of your site's world-readable files, such as /etc/passwd. III. Solution A. Sites that do not need to allow tftp access should disable it. This can be done by editing /etc/inetd.conf and deleting or commenting out the tftpd line: #tftp dgram udp wait nobody /etc/tftpd tftpd -n and then, as root, restarting inetd with the "refresh" command. # refresh -s inetd For more details on starting/stopping tftp, refer to documentation for the System Resource Controller (SRC) or the System Management Interface Tool (SMIT). B. Sites that must run tftpd (for example, to support X terminals) should obtain and install the above patch AND create a /etc/tftpaccess.ctl file to restrict the files that are accessible. The /etc/tftpaccess.ctl file should be writable only by root. Although the new /etc/tftpaccess.ctl mechanism provides a very general capability, the CERT/CC strongly recommends that sites keep this control file simple. For example, the following tftpaccess.ctl file is all that is necessary to support IBM X terminals: # /etc/tftpaccess.ctl # By default, all files are restricted if /etc/tftpaccess.ctl exists. # Allow access to X terminal files. allow:/usr/lpp/x_st_mgr/bin NOTE: Be CERTAIN to create the /etc/tftpaccess.ctl file. If it does not exist then all world-readable files are accessible as in the current version of tftpd. Installation Instructions: 1. Create an appropriate /etc/tftpaccess.ctl file. 2. From the directory containing the new tftpd module, issue the following commands as root. # chmod 644 /etc/tftpaccess.ctl # chown root.system /etc/tftpaccess.ctl # mv /etc/tftpd /etc/tftpd.old # cp tftpd /etc # chmod 755 /etc/tftpd # chown root.system /etc/tftpd # refresh -s inetd --------------------------------------------------------------------------- The CERT/CC wishes to thank Karl Swartz of the Stanford Linear Accelerator Center for bringing this vulnerability to our attention. --------------------------------------------------------------------------- ======================================================================== >(U)91232. Dualsession support for the 3151 Eureka! I found it, many of you may all ready know it but for those of you who don't .... you can get 2 virtual terminals on ASCII without JSB MultiView. All you need is a 3151 with the Cartridge for Connectivity. This will work on s1, s2, 8 port and on up. For more information on it look on HONE Doc Id Q558307 Item 7880H. Plus, it's a way to sell our terminals. It provides the same hot key support as is currently on the hft (uses a ctrl-shift-send sequence). Jan I was looking for an answer to a problem I am working on dealing with scales and time clock entry and happened to run across the reference to dual sessions on the 3151 (hence reference to Cartridge for Connectivity) here's what I know about it from "IBM 3151 ASCII Display Configuration and Software Guide" .. This cartridge provides: Automatic Dial - Automatic Dial Panel 4 Numbers Up to 60 Characters Hayes AT command mode and raw mode Dual Sessions By Hot Key - Single session by the main port Dual session by the main port Dual sessions by the auxilliary port and the main port Each session may be in any machine mode Session change by the hot key (ctrl-shift-send) Main port communications rs232c or 422 at 19.2 K host attachment (direct or via modem) Auxiliary Port communications rs232c interface at 19.2 for attachment to auxiliary devices or to hosts direct attachment modes 3151 PC (IBM code page 00437) 3151 PC MLP (ISO 8859/1.2) 3151 IBM System Attach 5 emulations emulations tvi 925PS IBM 3101 DEC vt220/vt100/vt52 ======================================================================== >(I)91233. Interface Builder for AIX As most of you probably know (we demoed it often enough on shows) we will be selling an interface builder with a future version of AIX. Rather like X.Desktop we have licenced this from a 3rd party and it is already availabl e for the RISC System. If you have customers interested in an interface builder for Motif you might suggest they buy UIM/X from: Anthony Lye Protek 2, Horton Industrial Park West drayton Middx. UB7 8JD UK Telephone: +44-895-446000 Fax: +44-895-448166 When I spoke with them they seemed very friendly and helpful. Cheers Iain ======================================================================== >(I)91234. Subset of the 2008 Update for the GTO and GL Those that want to run GL on the GTO graphics subsystem need the not yet available update 2008. Kingston made a preversion of the GTO parts of that update available. It contains only the GTO parts| We have it on our TOOLS disk. Get it with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET GTO2008 PACKAGE or TOOLS SENDTO DALVM41B IBMPC AIXDOC GET GTO2008 PACKAGE ======================================================================== >(U)91235. OEM rewriteable optical disks for the /6000 Alphatronix 2300 Englert Drive, Suite C, P.O. Box 13687 Research Triangle Park, NC 27709-3687 USA Phone (919) 544-0001 FAX (919) 544-4079 This company offers a stand-alone external rewritable optical disk in either a single or dual configuration of 650 MB each. The product uses the standard AIX device driver, allowing the optical disk to appear as a standard AIX journalled file system volume. As a result, the system can be booted from the optical drive, and super user privileges are not required for NFS access. Support for the Alphatronix jukebox (capacity from 10 GB to 100 GB) is planned for November 1991. Alphatronix dealers: Phone Sidus Systems Vancouver Canada (604) 682-2834 Toronto Canada (416) 882-1600 Montreal Canada (514) 731-9050 Nissho Tokyo Japan + 81-3544-8206 KCC Computer Seoul Korea + 822-771-58 Man Technology Seoul Korea + 822-782-7880 Tek-Hand Corp. Taipei Taiwan + 886-258-513-69 Arete Digital Bangalore India + 812-265-407 Cadam Research Auckland N. Zealand + 649-479-1100 Dataplus Periph. Lower Hutt N. Zealand + 644-693-882 Dios Optical Neutral Bay Australia + 612-953-0211 Dagang Teknik Petaling Malaysia + 603-719-8299 Newtech AS Oslo Norway + 472-648-330 Nextage Systems Oxford UK + 44-865-883-366 Compass Periph. Berkshire UK + 44-635-521-600 Has Computer BV Amsterdam Netherlands + 31-205-866-600 Has Belgium NV Antwerpen Belgium + 32-323-563-03 Note: For more OEM hardware stuff please check out OEMHW SCRIPT on AIXTOOLS. ======================================================================== ======================================================================== "Life may have no meaning -- or even worse, it may have a meaning of which I disapprove." > Table of contents: 91236. New distribution for AIXTIPS news because of classification needs 91237. Turning on GL trace 91238. COMPETITIVE SOFTWARE/SUPPORT PRICING INFORMATION 91239. Table of ASYNC Capabilities 91240. List of X/Open Publications 91241. /36 BASIC applications to AIX 91242. More BASIC applications to AIX 91243. Problems with the 2007 update ====================================================================== >(I)91236. New distribution for AIXTIPS news because of classification needs After some discussion with security people we found out that we have to request a justification for the access of confidential material in the news from our subscribers. Instead of stopping the whole news serverice and starting it again, we will continue to distribute the AIXTIPS as usual but limit the classification level of this distribution to "Internal Use Only". There still will be a confidential version of AIXTIPS NEWS distributed via another TOOLS disk. Access to this disk is given after the attached form was filled in and sent from the responsible manager. The confidential version will include the nonconfidential version as well, so those getting it will need to get only one version. The classification Cut here: ------------------------------------------------------------ AIXTIPS registration for IBM Confidential Tips This form should be filled in by the responsible manager and sent to AIXTIPS at MUNIVM4 from the managers user id. Name of the requestor: ______________________________ Userid: ________ at ________ Employee serial number: ________ Manger: ______________________________ Userid: ________ at ________ Business need to access IBM Confidential AIXTIPS NEWS: ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ Cut here: ------------------------------------------------------------ ======================================================================== >(U)91237. Turning on GL trace I learned something new tonight that I would like to share with members of the GL team. You ever get an application with some problem, but you don't have the source code to it, and you want to generate a GL trace for it? Well, it came to me tonight how to do it and the script below demonstrates how. Hope you enjoy this kind of information, Douglas Moore #|/bin/bsh # filename: gltrace_it # # usage: gltrace_it # # purpose: # Turn on GL trace for a program at run time # without modifying the application source or doing # some tricks with the linker or creating a special load module. # We use dbx. The script below runs the program with # dbx, stops in the first GL call (usually winopen) and # then sets the global variable that controls GL trace. # # GL trace only works in 3.1.2 at this time # # The GL trace output is appended to the ibmgl.trace file # which is kept in your current directory. # # some post processing may have to be done to make the # ibmgl.trace output file compilable. # # author: Douglas Moore # date: 11/1/91 # # program name if $# = 0 then echo "Usage: $0 program_name arg1 arg2 arg...." exit 1 fi echo ' stop in winopen run set $unsafeassign assign GLtrace=1 delete 1 cont cont cont ' dbx $* ======================================================================== >(I)91238. COMPETITIVE SOFTWARE/SUPPORT PRICING INFORMATION November 8, 1991 M&S Market Intelligence, Jon Mooy, recently completed an analysis of the hidden cost related to competitive software, support and documentation. The vendors examined were SUN, DEC, HP, and NCR.  In many situations when the hidden cost is included, the results favor the IBM RISC System/6000. This analysis is helpful when price is the deciding factor. The analysis consists of eleven charts which, for each of the competitors, describes the following: o Software components that are bundled with the hardware. o Terms and conditions for software and software service. o An eighteen month example of the cost of ownership for software, documentation and support for each of the competitors vs IBM. The charts reside on the MKTTOOLS conference disk. To obtain a copy enter the following commands from your VM command line: TOOLCAT MKTTOOLS GET RS6KSW$ PACKAGE The direct TOOLS command to get this is .... TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET RS6KSW$ PACKAGE The file RS6KSW$ has been compressed with TERSE and must be unpacked and the filetype changed to LIST3820 before printing. The following TERSE command should be used: TERSE RS6KSW$ TERS3820 A RS6KSW$ LIST3820 A (UNPACK After the file is unpacked it can be printed on a 3820 printer using print programs which support list3820 graphics (example: pmprint, foils5) CONTACT: AARTALE at RHQVM05 ======================================================================== >(U)91239. Table of ASYNC Capabilities Michele, following is a table of Async modem signal line support status and baud rates supported for the 8 port, 16 port, and 64 port communications adapters. This information will be supplied to the field and appear in future documentation. MODEM CONTROL LINE SUPPORT BY ASYNC PRODUCTS OFFERED SIGNAL DESCRIPTION IN/OUT 8 PORT 16 PORT 64 PORT ____________________________________________________________________________ DTR DATA TERMINAL RDY OUT SUPPORT SUPPORT SUPPORT DCD DATA CARRIER DET IN SUPPORT SUPPORT SUPPORT CTS CLEAR TO SEND IN SUPPORT NO SUPT SUPPORT RTS REQUEST TO SEND OUT SUPPORT NO SUPT SUPPORT DSR DATA SET READY IN SUPPORT NO SUPT NO SUPT RI RING INDICATOR IN SUPPORT NO SUPT NO SUPT ____________________________________________________________________________ AIX SUPPORTED BAUD RATES 8PORT 16PORT 64PORT __________ _______ _______ _______ 50 50 50 * 75 75 75 75 110 110 110 110 134.5 134.5 134.5 * * The 64 Port UART hardware 150 150 150 150 is capable of operating 200 200 200 * at these baud rates, but 300 300 300 300 vendor propriatary firmware 600 600 600 600 does not support them. 1200 1200 1200 1200 1800 1800 1800 1800 It does however support 2400 2400 2400 2400 2000 and 3600 BAUD in 4800 4800 4800 4800 addition to the AIX supported 9600 9600 9600 9600 BAUD rates. 19200 19200 19200 19200 38400 38400 38400 38400 ======================================================================== >(U)91240. List of X/Open Publications The current list of X/Open publications and estimated dates for further publications is attached for your information. Regards Cathy ---------------------------------------------------------------------------- Cathy Hughes X/Open Company Limited Apex Plaza, Forbury Road, Email: cy.hughes@xopen.co.uk Reading, Berkshire, Tel: +44 734 508311 ext 2261 RG1 1AX, England Fax: +44 734 500110 Tel: +44 734 508311 ---------------------------------------------------------------------------- X/Open Specifications --------------------- X/Open specifications (post-XPG3) currently available are as follows: [S = Snapshot, PS = Preliminary Specification, G = Guide, DS = Developers' Specification, CS = CAE Specification, AD = Addendum] Title Date published ----------------------------------------------------------------- [PS] Byte Stream File Transfer (BSFT) June 1990 [S] Comparison Study of OSI Profiles August 1990 [DS] ISAM August 1990 [DS] Protocols for X/Open PC Interworking: (PC)NFS August 1990 [DS] SQL August 1990 (This is superseded by SQL PS, July 1991) [PS] DTP: The XA Specification September 1990 (This is superseded by DTP/XA S, June 1991) [S] Security: Auditing and Authentication October 1990 [DS] CPI-C November 1990 [PS] API to Directory Services (XDS) December 1990 [S] Interworking API Style Guide December 1990 [DS] Revised XTI December 1990 [PS] API to OSI Object Management (XOM) January 1991 [G] Security Guide (Second Edition) February 1991 [DS] Protocols for X/Open PC Interworking: SMB March 1991 [PS] API to Electronic Mail (X.400) April 1991 [G] Guide to the Internet Protocol Suite (IPS) April 1991 [PS] X/Open CD-ROM Support Component (XCDR) May 1991 [S] DTP: The XA Specification June 1991 [CS] Protocols for X/Open Interworking: XNFS July 1991 [PS] SQL July 1991 [S] RDA for SQL July 1991 [CS] X/Open Window Management: X Protocol July 1991 [CS] X/Open Window Management: Additional Specs July 1991 [CS] X/Open Window Management: Xt Toolkit July 1991 [CS] X/Open Window Management: Xlib August 1991 [S] Systems Management: Problem Statement August 1991 [AD] XTI Addendum August 1991 [PS] IPC Mechanisms for SMB August 1991 [G] DTP: Reference Model October 1991 [G] Guide to Selected X.400 & Dir Services APIs November 1991 X/Open specifications available in printed form in the near future are as follows: Title Estimated date ----------------------------------------------------------------- [S] Systems Management: Reference Model November 1991 [G] IPS-OSI Coexistence & Migration Guide November 1991 [S] Basic Definitions December 1991 [S] System Interfaces and Headers December 1991 [S] Commands and Utilities December 1991 [CS] API to OSI Object Management (XOM) January 1992 [CS] API to Directory Services (XDS) January 1992 [CS] API to Electronic Mail (X.400) January 1992 [PS] EDI Messaging Package (XEDI) January 1992 [CS] COBOL Language January 1992 [CS] IPC Mechanisms for SMB January 1992 [PS] Message Store API February 1992 [G] Internationalisation Guide February 1992 [CS] Byte Stream File Transfer (BSFT) February 1992 All enquiries regarding orders should be directed to the following address: X/Open Company Limited (Publications) PO Box 109, Penn High Wycombe, Bucks HP10 8NP England Tel: +44 494 813844 Fax: +44 494 816849 ======================================================================== >(U)91241. /36 BASIC applications to AIX In the UK there is a company called Communic8 that has a product which enables System 36 applications to run unchanged on the Risc System 6000. Address is; Communic8 9 The Old Power Station 121 Mortlake High Street London SW14 8SN Phone 081 392 1250 I do not know if its sold outside the UK Barry Mellish ======================================================================== >(U)91242. More BASIC applications to AIX There is a company here in Austin that is VERY well versed in BASIC and moving them from one platform to another. They have a product that is a translator form BASIC to C. They handle a rather large variety of BASIC dialects. They also have the working environment of many platforms as well. As such they can take an application written in say DEC BASIC, and translate it, compile it (with the local C compiler), link in the source machine's environment, and presto, the application runs on our machine just as if it were on the source platform. The C source produced is quite good and very readable. A vendor moved all their source from a BASIC base to a C base with their package and now code in C. The company is: Software Translations 1114 Lost Creek Blvd Austin, TX 78746 Voice - (512) 327-6001 FAX - (512) 327-6005 Talk to Jon Powers (he's the main dude). Jaime Vazquez ======================================================================== >(U)91243. Problems with the 2007 update SNA users SNA users should not apply 2007 until they have called AASC and ordered fix ix23327. When this fix is received, apply 2007 and then the fix before attempting to start SNA attachment. Xstation Users You will not be able to apply the update to Xstation Manager. If your x_st_mgrmEn_US.msg level is 1.1, you will not be able to install the 1.2 level of messages. If you have already received fix ix21263 or ix19251 you have the same level of code that is on 2007. Otherwise, you should call AASC and order emergency fix ix21263 in lieu of installing and updating Xstation and Xstation Manager messages. SETUID/SETGID Shell Scripts A fix for a potential security risk dealing with the use of the SETUID and SETGID permission bits on shell scripts is included in the 2007 update. Prior to 2007, when a shell script was executed whose permissions included the SETUID bit (set user-id), the shell script ran with the permissions of the shell script's owner. Similarly, if the SETGID bit (set group-id) was set, the shell script ran with the permissions of the shell script's group. Beginning with 2007 update, the SETUID and SETGID permission bits will no longer be supported for shell scripts. This change will NOT effect compiled programs. Examples removed If your application requires the previous SETUID behavior, you can call the shell script from a small compiled program that has the SETUID bit set in it's permissions. - Create a C program similar to the following named execsh.c main(int argc, char *argv) execvp("shell.sh", argv); /* execute the shell script */ exit(1); - Compile and link execsh.c using the command : cc -o execsh execsh.c - Set the owner of the execsh to root and the SETUID bit on chown root execsh chmod 4755 execsh The SETUID behavior has not changed for compiled programs, so execsh will 'effectively' become root when it is executed, and will pass this permission to shell.sh. ======================================================================== ======================================================================== Subject: IBM's Software Development Ever wondered how IBM software products are developed ? Here is the chance to get a secret look at the process. Bear in mind that the following is truly "IBM internal use only" information | :-) %%Gerhard Strobl (:-=0) ======================================================================= LIFE CYCLE OF A NEW IBM PRODUCT ( How IBM would develop an umbrella) 1.CODENAME: UMBRELLA 2.PRODUCT SPECIFICATION: multifunctional, integrated, user-friendly and non-expensive "solution" compatible with future system architecture concepts aimed at avoiding the effect of extensive humidity and other environmental influences to human heads and other body parts. 3.MARKETING SPECIFICATION: Get hold of it | Now | Pre-Version: Type: Hazelnut-stick (because of strict confidentiality, the shape of the product can only be guessed at). Beta-Version: Plastic tarp sized 5 square meters including 320 pages of technical documentation. Golden Version: 5-color pamphlet, sunny weather report and about 4-15 months postponement of GA (general availability). Release 1.0: Frame without covering; the mechanism is working reasonably, it unfolds effortlessly, but there are problems with folding it again. The handle is offered as a separate feature with its own order number. Release 1.1: Frame without covering, fully integrated handle, mechanism is working problem-free. Development is praising the well thought-out design, marketing stresses the products' universial usability. The weight of 18.9kg is to be addressed in one of the next releases. The opening mechanism takes about 12.5 minutes at the moment, but is caused by the hypermodern microscalar hydraulics being used for the first time in a worldwide product of this type. IBM announces plans for further performance improvements. Release 2.0: Milestone in development: the product is delivered with full (|) covering. The customers criticize only one item: IBM should use watertight materials for the covering. Release 2.1: The covering is now watertight, but the opening mechanism doesn't work anymore. Marketing tries to place the product as a sun-shade; development thinks about functional extensions such as a suitable leather bag. As a second variant, IBM considers the involvement of a new Business Partner. The Business Partner cannot deliver a product, but he promises a rain-dance to avoid tropical rains. Release 2.2: Suitable leather bag is being developed. Marketing praises the architectural concept of a non-opening umbrella with a suitable bag (an open umbrella wouldn't fit into the bag anyway, right ?). Release 3.0: Upgrade to a fully functional model with watertight covering - free of charge | For this, IBM unfortunately had to change the dimension of the leather bag, so the customers have to buy a new version which is twice as expensive as before. Release X.X: Development defends itself against repeated attacks by stating that the product passed various test cycles and that no involved tester could find any functional deficiencies. Final: Product development is transfered from a lab in Saudi Arabia to a lab near London. Walt Smith - T/L 444-6802 >91.11.18 Table of contents: (U)91244. BSD/Posix line discipline clash on ptys (U)91245. CISCO routers and the /6000 (I)91246. DOCUMENT ABOUT NEW GTx GRAPHICS HARDWARE ON ICTIPS (U)91247. ORACLE CLIENT SERVER PROBLEM (I)91248. RISC SYSTEM/6000 FACTS & FEATURES CUSTOMER DELIVERABLE (I)91249. graPHIGS Hardcopy/Metafile requirements (U)91250. RISC System/6000 Parts list. (U)91251. Getting Redbooks without Sweating (U)91252. PRIME to RISC System/6000 migration (I)91253. TCP/NetBIOS FOR OS/2 - TCP/IP V1.2 SUPPORT (C)91254. AIX 3.2 maintenance mode (U)91255. 64 PORT PROBLEMS fixed in 2006 (U)91256. Get an EXABYTE 8500 tape to work on an IBM RS/6000 (3.1.5) (U)91257. RS/Magazine ======================================================================== >(U)91244. BSD/Posix line discipline clash on ptys Form the Internet on comp.unix.aix: Well, with some information from a friendly netter, I was able to fix this problem myself. Hopefully, the 3.1.7 update will be out soon, and this will be fixed permanently. The problem is that some programs change the PTY line discipline to "bsd".1 login apparently hangs if it's not "posix". My solution, of course, is to put a small preface on login to fix this. To illustrate: roothal 1% cd /bin roothal 2% mv login ologin roothal 3% cat > login #|/bin/sh /bin/stty disp posix exec /bin/ologin $* ^D roothal 4% chmod 555 login roothal 5% chown root.security login roothal 6% This seems to fix the problem. (THANK GOD||) Note that the 'login' script should *not* be setuid, due to the normal cavaets about setuid shell scripts. It's not necessary anyway, since ologin is still setuid. Enjoy| From mycrofthal.gnu.ai.mit.edu (Charles Hannum) ======================================================================== >(U)91245. CISCO routers and the /6000 Another one form the Internet: comp.unix.aix Hello Everybody, First of all I really want to thank everyone who posted and wrote to me to help solve the problem of my RS6000 not being able to communicate with my CISCO router. It turns out that several people have this problem and I think it is important enough to summarize what I have learned(and the solution) for all of you. Here is the bottom line: Recently(around September aparantly), IBM began to use a new version of its ethernet card. This new version is known as a Revision 3 card. The cards that I believe most people have is called a revision 2 card. The card that I had had 1990 printed on the board. This new card does not work with CISCO's. I got several notes saying this was the problem. Two notes were specific. One claimed the revision 3 card "..Has a packet alingment problem. Any packets send by these cards are thrown out by the CISCO router." Another message I got claims "The rev 3 card apparently allows dribble bits to be sent which the router has problems with; rev 2 card did not." I do not know of anyone who has managed to fix this problem in any other way then using an older version of the ethernet card(This is what I did, IBM brought me an old card which now works fine.) One poster claims the problem "Can supposedly be fixed by an upgrade to the CISCO router microcode..although we haven't gotten that yet or tried it. So if you have a CISCO and you are planning on buying a new IBM RS6000 you may want to talk to IBM about what version of the card they put into your machine. Here in Italy they didn't seem to know there were seperate versions. All I really know is that my new card is "about a year old." If anyone from IBM would like to clear up some of the specifics about this I(and several others) would be very appreciative. Once again thatk you for all your help and I hope this is usefull. From waltercithe501.cithep.caltech.edu (Chris Walter) ======================================================================== >(I)91246. DOCUMENT ABOUT NEW GTx GRAPHICS HARDWARE ON ICTIPS In July 1991 the new graphic cards for the RS/6000 have been announced. You can find on the AIXTOOLS a script document which describes: - the new graphics hardware (Gt3, Gt4, Gt4x) - technical background information about graphic techniques - information about the new GPC benchmarks. To get this document, type at the OFFICE command line: TOOLS SENDTO MUNIVM4 AIXTOOLS ICTIPS GET GTX SCRIPT As this disk is only for confidential stuff, you have to be authorized to get the document. See the header of this file for acess info. To print the document, simply use ICPR or any other BookMonster formatter. Please don't be confused because of some errors which you get with ICPR. Print the document anyway. This document came originally from ITSC Austin and cannot be printed properly in our environment. I don't know Bookmaster well enough to correct this. I took the part with unannounced products out of it. The document is still IBM CONFIDENTIAL because of the technical information in it. I hope it is valuable for you. A. Hermelink 7.11.91 ======================================================================== >(U)91247. ORACLE CLIENT SERVER PROBLEM With Oracle running on two RS/6000s (one as server, one as client) the following problem may occur: When the Oracle server breaks, the client does not recognize the malfunction, the client process simply hangs without showing an error. THIS IS NOT A PROBLEM OF OUR TCP/IP IMPLEMENTATION AS ONE MAY THINK. We tested some cases at Oracle Munich with Oracle V.6.0.31 and SQLNet V.1.2.7.1.7: 1. When the server database of a running server is shutdown with "SQLDBA shutdown abort", the client in fact does not recognize it and hangs... (We tried it also with an HP machine running as server with newer software levels, Oracle V.6.0.32, SQLNet V.1.2.7.2.1. In this case the client stopped with showing "603: Serious Error occured".) This is not a problem of our TCP/IP, Oracle has to implement an additional functionality to test this case, eg. a daemon which tests periodically the database and informs the clients if the database is down. And, as we see with HP, a newer Oracle software level has this functionality. 2. When the server shadowprocess for the client is killed but the database is still running, the client process stops and shows "3113: Error during connect". This works as desired. 3. Client and server are running, the server is physically detached from the network. Result: The Client hangs, after about 10 minutes the error message "3113: Error during connect" is shown and the client process stops. This is normal TCP/IP functionality, the connection is lost and the keep alive timer is running out. After this time the connection is closed. For a faster error indication, oracle has to implement its own network monitoring. 4. Client and server are running, the server is switched off. Same as case 3., normal TCP/IP functionality. Summary: Oracle has a lack of functionality regarding client-server operations in the current software level on the RS/6000, newer versions test this cases. Our TCP/IP is working correctly. A. Hermelink 6.11.91 ======================================================================== >(I)91248. RISC SYSTEM/6000 FACTS & FEATURES CUSTOMER DELIVERABLE RISC SYSTEM/6000 FACTS & FEATURES CUSTOMER DELIVERABLE - NOW AVAILABLE ON MKTTOOLS November 12, 1991 RISC System/6000 Facts & Features is available on the tools disk MKTTOOLS. This 2-page document contains the latest performance and configuration information for RISC System/6000 POWERstations and POWERservers. In addition, an entry configuration and entry price is given for each model. To access the file on the tools disk, type the following command at your PROFS command line: TOOLCAT MKTTOOLS GET RS6KFF PACKAGE or use the TOOLS command EXEC TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET RS6KFF Because of its size, the file has been "tersed". To unpack it for printing, type the following command on your PROFS command line: TERSE RS6KFF TERS3820 A RS6KFF LIST3820 A (UNPACK Then, print RS6KFF as you would any LIST3820 file. RISC System/6000 Facts & Features (G3 20-9878) is still available from Mechanicsburg. ======================================================================== >(I)91249. graPHIGS Hardcopy/Metafile requirements The development team for graPHIGS plotting software is currently in the process of gathering requirements for future enhancements and extensions to the graPHIGS plotting utilities. We would appreciate it if anyone who may have concerns or comments in this area would respond to a series of questions placed in the GPOUTPUT FORUM on the IBMUNIX conference. graPHIGS development has created the GPOUTPUT FORUM in order to gather requirements for graPHIGS hardcopy and metafile output capabilities. We encourage you to use this forum for discussions of your requirements in this area. However, technical questions or comments regarding graPHIGS output should still be directed to the GRAPHIGS FORUM. Topics include: Pen Plotting, Raster Plotting, PostScript, Graphical Metafiles (CGM, GDF, ADMGDF) Your response will be greatly appreciated. Thank you. graPHIGS Development ======================================================================== >(U)91250. RISC System/6000 Parts list. PRODUCT F.R.U. NAME / TYPE PART No. ******************************* 7012 CARD LATCH 40F9969 7013 CARD LATCH 59F4089 DISKETTE REDRIVER CARD 53F3417 DISKETTE DRIVE 3,5" 53F3423 FLOPPY RISER 11F8890 I/O SLOT PLANAR 81F7722 STANDARD I/O PLANAR 53F3345 7012-32H CPU 81F8232 7012-320 CPU 91F1009 7013-520 CPU 71F1378 7013-530 CPU 81F7888 7013-540 CPU 53F3349 7013-550 CPU 81F8008 7015-930 CPU 53F3350 7012 BASE PLANAR 71F0157 7010-120 PLANAR 59F4492 7010-130 PLANAR 81F7808 POWER 7010-120/130 71F0066 POWER S. 7013 81F7883 (mod. 520, 530, 540) POWER S. 7013 G2520 (mod. 520, 530, 540, 550) POWER S. 7012 91F0844 (mod. 320) POWER S. 7016 71F0069 (mod. 730) POWER SUPPLY 72XX 81F9128 BATTERY 23F0168 MEMORY 64 mb 81F8926 base card w/o SIMMS(no mod.540) MEMORY 8-16-32-64 mb 71F1395 base card w/o SIMMS (mod.550) MEMORY 32 mb 59F4436 base card w/o SIMMS (mod.540) MEMORY 32 mb 81F8926 base card w/o SIMMS MEMORY 8 or 16 mb 59F4433 base card w/o SIMMS SIMM (8mb x 8) 70F9976 ( 64 MB ) SIMM (4mb x 8) 70F9973 ( 32 MB ) no mod.540 SIMM (4mb x 8) 59F4583 ( 32 MB ) mod.540 only SIMM (2mb x 8) 59F4582 (16 MB) SIMM (1mb x 8) 59F4581 ( 8 MB) 120 MB DISK DRIVE 53F3425 (DBA) 160 MB DISK DRIVE 81F8071 (DBA) HARDF. RISER 7012 81F8900 (120 or 160MB) 320 MB HARDFILE 93X0961 355 MB HARDFILE 53F3427 400 MB HARDFILE 73F9001 670 MB DISK DRIVE 53F3429 857 MB LOGIC ASM. 95X2346 857 MB HDA 95X2431 (HDA ONLY) SCSI ADAPTER CARD ASM G2369 SCSI MINIFUSE 1A 40F9736 EXT.SCSI CABLE 70F9733 EXT.SCSI CABLE (HA) G1897 EXT.SCSI-SCSI CABLE 70F9734 EXT.SCSI TERMINATOR 15F6743 EXT.SCSI-SCSI TERMINAT. G0968 (BLUE TERMINATOR) INT.SCSI TERMINATOR 70F9900 150MB 1/4" TAPE DRIVE G2636 8mm TAPE DRIVE 91F0847 CD-ROM DRIVE ASM 53F3422 MOUSE 11F8895 ETHERNET CARD ASM G3529 GRAPHIC I/O CARD (GIO) 22F9758 GRAPHICS ADAPT. MONO 71F1224 GRAPHICS ADAPT. COLOR 71F1223 MGE2 COLOR GRAPHIC 42F6842 MRV2 COLOR GRAPHIC 71F1151 8 BIT COLOR GRAPHIC 71F1117 24 BIT COLOR GRAPHIC 71F1114 MZB1 CARD Z-BUFFER 42F6889 MSLA CARD ASM. 39F8312 MULTIPROTOCOL BASE 53F3407 MULTIPROTOCOL DAUGHTER 53F3408 MULTIPROTOCOL FAN OUT 40F9897 (CABEL INCLUDED) RISER CARD 7010-120 59F3736 TOKEN RING G2652 X25 INTERFACE ADAPTER 41F0635 8 PORT RS232 ADAPT. 40F9778 8 PORT RS422 ADAPT. 40F9766 16 PORT RS232 ADAPT. 30F9297 16 PORT RS422 ADAPT. 30F9299 16 PORTS FANOUT 53F3311 64 PORT ADAPTER G1168 64 PORT CLUSTER 91F0817 TCA (3270) ADAPTER 42F6717 CABLE S1-RS232-3151 G0943 KEYBOARD 1394545 Compiled by Tina Mattson ======================================================================== >(U)91251. Getting Redbooks without Sweating I am sure many of you know this ... but those of you that don't... You can order all Redbook in a particular area. To do this for AIX order GBOF-2198 Mark Johnson Advisory Systems Engineer ======================================================================== >(U)91252. PRIME to RISC System/6000 migration PRIME TO RISC SYSTEM/6000 ENABLER OFFERS 40X PERFORMANCE IMPROVEMENT| November 14, 1991 Do you have customers or prospects using Prime computers? Are they looking for improved performance and capacity, better support and lower monthly costs? If YES, read on... Datamann Inc., an IBM RISC System/6000 industry remarketer and former Prime remarketer, now offers Prime users a simple, fast migration to the RISC System. By utilizing a set of high-performance utilities or "enablers" to emulate the Prime environment, most applications written in COBOL, FORTRAN, PL/1 and/or MIDASPLUS and running under PRIMOS (Prime's proprietary operating system) can be loaded and run on the RISC System, without source code modification| Once the application has been loaded using a direct one-for-one emulation library, it will operate identically in the new RISC System/6000 environment. Performance based on a recent benchmark provided astonishing results. A job taking two hours to run on a Prime 6350 took only 3 minutes on a RISC System/6000 model 530| Other major benefits to Prime users include: * Significantly reduced monthly costs * Comprehensive IBM service * Enhanced performance * Improved capacity and expandability For more information or to determine how your Prime customer or prospect can benefit from Datamann's services, contact John Mann at Datamann, (802) 295-6600. Questions on this notice are to be forwarded to Deb Light, BOSTON(DJLIGHT). ======================================================================== >(I)91253. TCP/NetBIOS FOR OS/2 - TCP/IP V1.2 SUPPORT November 15, 1991 NetBIOS for TCP/IP (TCP/NetBIOS) was announced 3/19/91 to permit customers to run NETBIOS over TCP/IP networks. This allows the customer to grow their NetBIOS applications over local and wide area networks using a common open network protocol, TCP/IP. OS/2 workstations using OS/2 1.2/1.3 EE can use NetBIOS applications directly over a local area network using the support in Extended Edition for NetBIOS. As networks using NetBIOS grow in size, both in the number of workstations, and grow to include wide area networks, it can become impractical to use the native NetBIOS support. The TCP/NetBIOS program can allow those networks to grow by using TCP/IP network protocols rather than NetBIOS on the network. The same applications can still be used because the NetBIOS application interfaces are supported using TCP/NetBIOS. The TCP/NetBIOS was announced with support for OS/2 TCP/IP V1.1 which could be used with OS/2 EE V1.2 In October the new OS/2 TCP/IP V1.2 became available. It can run with OS/2 1.3 SE/EE or OS/2 2.0. In order to run TCP/NetBIOS with OS/2 TCP/IP 1.2 the customer will need to get a CSD, corrective service diskette. The customer will need to create an APAR to obtain the CSD. Effective with this CSD the customer can grow their TCP/NetBIOS network using the latest release of TCP/IP for OS/2. Contact: ALAN REINHOLD at 8/352-2552 or REINHOLD RALYDPD ======================================================================== >(C)91254. AIX 3.2 maintenance mode The /etc/continue command used during diskette maintenance mode has been replaced by getrootfs. The syntax remains the same (ie. getrootfs hdisk0). Mickey ======================================================================== >(U)91255. 64 PORT PROBLEMS fixed in 2006 For both new installs and old systems that have 64 port cards we recommend that PTF U401343 (2006) or higher be applied. It is an excellent base to start on when using the 64 port card LONGORRA at AUSVM8 ======================================================================== >(U)91256. Get an EXABYTE 8500 tape to work on an IBM RS/6000 (3.1.5) Modify the file /etc/objrepos/PdAt: (scsi/tape/8mm) PdAt: dev_type=5 model_name=EXB-8500-85Qanx0 mode_data=0x000010080000000000000400 As root run the '# cfgmgr' command. After a reboot the entries were reset to the AIX 3005 default(s). Maybe we also have to modify the file /etc/objrepos/boot/PdAt to make it a permanent change. An other solution is to create a small shell script using 'odmget', 'odmadd' or the 'odmchange' command to do the changes on each reboot. Frank Kraemer ======================================================================== >(U)91257. RS/Magazine For those who are interested... I have spoken with the folks at RS/Magazine (Computer Publishing Group) - the same folks who put out SunExpert and inquired about the FREE subscription offer. Here is the current status: It is currently available for IBMers and Customer in the US + Canada and IBMers outside of the US and Canada (they are still deciding if it will be offered to customers outside the US and Canada). What do I need to do: Send in the free subscription card How do I get one: Send an e-mail to Debbie Moore - dm@expert.com and request a free subscription card for the RS/Magazine. She will send you one (or more). Or call her at (617)-739-7001. What if I don't: Subscription price will start in 1992 (January) at a rate of $49.50 (in the US + Canada) and $70.00 outside the US. I do not speak or represent them. Standard disclaimers apply... Stephen A. Laufer ======================================================================== ======================================================================== "A programmer is a person who passes as an exacting expert on the basis of being able to turn out, after innumerable punching, an infinite series of incomprehensive answers calculated with micrometric precisions from vague assumptions based on debatable figures taken from inconclusive documents and carried out on instruments of problematical accuracy by persons of dubious reliability and questionable mentality for the avowed purpose of annoying and confounding a hopelessly defenseless department that was unfortunate enough to ask for the information in the first place." -- IEEE Grid newsmagazine >91.11.26 Table of contents: (I)91258. ESSL presentation guide now available on MKTTOOLS (U)91259. AIXPERT PUBLICATION: FALL 1991 ISSUE AVAILABLE (U)91260. FAQ list for aix 3.1 formatted for a 3820 (U)91261. IBM 3151 Emulator Software for PC's (I)91262. AIX Printer Files for the IBM 4029 and 4019 LaserPrinters (U)91263. Oberon for the RS/6000 (U)91264. Free NQS on R/6000-550 (U)91265. NLS and HCON (I)91266. Defect problem reporting in HONE for Germany (U)91267. AIX Component IDs ======================================================================== >(I)91258. ESSL presentation guide now available on MKTTOOLS November 20, 1991 The Engineering & Scientific Subroutine Library (ESSL) Presentation Guide is now available on the MKTTOOLS conference disk. ESSL is an application accelerating Math subroutine library for ES/9000 RISC System/6000 FORTRAN and 'C' programs. To request the presentation guide package use your conference disk interface or issue the following command from your PROFS/Office Vision account: TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET ESSLR4 PACKAGE For more information contact Marc Lipnick (T/L 752-7324, DFWVM04(LIPNICK). ======================================================================== >(U)91259. AIXPERT PUBLICATION: FALL 1991 ISSUE AVAILABLE November 22, 1991 The AIXpert is a quarterly technical publication for software developers working on AIX platforms. Fall issue contents: * OSF's distributed computing environment * Distributed computing tools from Transarc * Dynamic Binding in AIX Version 3 * AIX/ESA * Creating LU6.2 profiles for SNA Services/6000 * Q's and A's from the Dallas AIX Technical Support Center ... and more. Available from Mechanicsburg - order number G580-0008 Subscription information: * IBM employees should use SLSS (available via HONE). Publication number is GBOF-1199. (To request access to HONE, call 1-800-234-2414) * Software developers - call the software vendor information line at 1-800-626-8363 - FAX a request to Gloria Hardman at 203-783-7669 - send -email to hardmanrhqvm21.vnet.ibm.com The following back issues are still available from Mechanicsburg - * Summer graphics issue - G580-0007 * Spring issue - porting guide - G580-0006 Please address questions or comments to RHQVM21(HARDMAN) ======================================================================== >(U)91260. FAQ list for aix 3.1 formatted for a 3820 I formatted the FAQ (frequently asked question) on AIX 3.1 as a script/list3820 document to be printed on 3820 printers. The faq list is distributed on the Internet and maintained from B. Engsig (Oracle). Before printing please unTERS the file and remane it to FAQ LIST3820. Get it from the internal TOOLS disk with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXFAQ TERS3820 or TOOLS SENDTO DALVM41B IBMPC AIXDOC GET AIXFAQ TERS3820 have fun --frank Frank Kraemer ======================================================================== >(U)91261. IBM 3151 Emulator Software for PC's I have a contact for anyone that is looking for an emulator that will run on a PC and look like an IBM 3151 terminal. This code works pretty well and will even work in a TCP/IP environment. The product is called E3151PC. RD Enterprises 603 Newport Avenue Altamonte Springs, FL 32701 407-831-6118 As always, I have no personal interests, etc... in the above product. Larry Collings AIX SE Orlando, FL ======================================================================== >(I)91262. AIX Printer Files for the IBM 4029 and 4019 LaserPrinters Available via VM Request Printer colon files for the IBM 4029 LaserPrinter and the IBM 4019 LaserPrinter for use with AIX Version 3.1.5 for the RISC System/6000 are now available via VM Request. To get the 4029 Package: REQUEST AIX4029 FROM DRIVERS AT LEXVMD To get the 4019 Package (4019.ps file for Emulation/Mode switching): REQUEST AIX4019 FROM DRIVERS AT LEXVMD These files are also available from the Lexmark Customer Support line, 606-232-3000. And the 4029 package is available from the Lexmark Bulletin Board, 606-232-5653. J. D. Lewis Lexmark International ======================================================================== >(U)91263. Oberon for the RS/6000 Oberon 2.2 for the IBM RISC System/6000 ======================================= I'm pleased to announce the availability of OBERON 2.2 from ETH Zurich. Oberon for the IBM RISC System/6000 can be obtained using anonymous ftp from neptune.inf.ethz.ch 129.132.101.33 under the directory Oberon/RS6000. gatekeeper.dec.com 16.1.0.2 contains a copy of the distribution. The implementation supports the Oberon-2 language extensions as described in the file Oberon/Docu/Oberon2.Differences.ps.Z. Please see the file README for further information about the particular implementation for the IBM RISC System/6000. The primary source for documentation about the Oberon system is: M. Reiser, The Oberon System, User Guide and Programmer's Manual Addison-Wesley, 1991, ISBN 0-201-54422-9 (Note that hardware specific details like screen bitmap organization or timer resolution may differ between implementations). Additional documentation is available as compressed postscript files under Oberon/Docu . The following gives you a brief overview of what Oberon is. Oberon is both, a programming language and a programming system designed by N. Wirth and J. Gutknecht at ETH Zurich. The language Oberon evolved from Modula-2 with some modifications: - definition and implementation merged into one document - type extension (for object-oriented programming) - support for runtime type tests - type inclusion for numeric types - string operations - enumerations and subranges dropped - Oberon-2: type-bound procedures, read-only export, open arrays Compilers - generate native code - speed: about 1600 lines per second on a RS/6000 Model 530 - no separate linking step required System - single-process multi tasking - automatic garbage collection - multiple module entry points (commands) - runtime linking - tiled windows - texts as built-in abstract data type - extensible tools for text and graphics editing Oberon has been used for education, personal computing, and program development at ETH Zurich for more than three years now. Oberon is available from ETH for the following workstations: Apple MacIntosh II, Sun SPARCstation, DEC DECstation and the IBM RS/6000. All versions can be found on neptune.inf.ethz.ch and gatekeeper.dec.com. Marc-Michael Brandis Computer Systems Laboratory, ETH-Zentrum (Swiss Federal Institute of Technology) CH-8092 Zurich, Switzerland email: brandisinf.ethz.ch ======================================================================== >(U)91264. Free NQS on R/6000-550 From: shahfnsony.fnal.gov (Hemant Shah) Date: 8 Nov 91 18:07:56 GMT Sender: newsfnnews.fnal.gov Organization: Fermi National Accelerator Laboratory, Batavia, IL Nntp-Posting-Host: fnsony.fnal.gov You can get a copy of the source and docs via anon ftp to archive.anu.edu.au (150.203.2.2), look in ftp/pub/src/applications/nqs.tar.Z I got my copy from here, all I had to do was copy appropriate makefile and type "make" it compiled without any problem and I was able to configure it. Hope this helps :-) ======================================================================== >(U)91265. Suppressing XLF run-time I/O error messages >From markusoahu.cern.ch (Markus Baertschi) Newsgroups: comp.unix.aix To suppress these run-time messages you can set an environment- variable. Using ksh you can use 'export xrfmessages=no'. If you want this to be the default on your machine you can put this into your /etc/environment. Markus -- Markus Baertschi, AIX Support at CERN (European Particle Physics Research) ======================================================================== >(U)91265. NLS and HCON If you have NLS problems with HCON try to set NLIN and NLOUT to point to the right translation table before starting HCON. For Germany use: NLIN=/usr/lib/nls/nlin/GR.in NLOUT=/usr/lib/nls/nlout/GR.out ======================================================================== >(I)91266. Defect problem reporting in HONE for Germany There is a text on our TOOLS disk that tells SEs how to report problems in HONE so that they do not need to wait on the busy defect support line. This text is in German. Get it with: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET SEINFO GERMANY We suggest that German SEs use this instead of calling the hotline. The hotline should be used for customers who have no access to the HONE method. ======================================================================== >(U)91267. AIX Component IDs 3.1 AIX 3.1.x (RISC/6000) ----------------------------- Compid Programname Release ------------------------------------- 575603001 OPSYS 3.1.0 575603002 KRS (Info Exp) 560126301 PC-Sim 1.1.0 560125701 Xwindow Env 1.1.0 560125702 MOTIF 560125703 Desktop 560145701 Xstation MGR 1.1.0 570629101 ADA/6000 CMP 1.1.0 570629401 ADA RTE 1.1.0 570629101 ADA/6000 CMP 2.1.0 570629401 ADA RTE 2.1.0 560124801 XL Fortran CMP 1.1.0 560126601 XL Fortran RTE 1.1.0 576501800 XL Fortran CMP 2.1.0 576501900 XL Fortran RTE 2.1.0 560125401 XL Pascal CMP 1.1.0 560125101 XL Pascal RTE 1.1.0 560125801 XL Cobol CMP 1.1.0 560125901 XL Cobol RTE 1.1.0 560124901 C Compiler 1.0.0 560128701 SNA Services 1.1.0 560126001 3270 HCON/6000 1.1.0 560126001 3270 HCON/6000 1.2.0 560125601 3278/79 Emul 1.1.0 560125301 Network Mgrmnt 1.1.0 560138401 Graph User Env 2.2.0 560101101 MultiView 573007801 Viaduct AS400 562101301 Optimiz. Library 560138601 Graph.I.Toolkit 560125001 TCP/IP 1.1.0 560125201 Text Data For 560126201 NFS 1.1.0 560128401 BASIC APPL.DEV 560145601 Neches Server 562101201 AIX OS V3 PKG 562102901 Windows DBCS 570629101 NFS Encrypt 576502400 AADU V.2.1 576502500 XONDOS V.2.1 3.2 AIX 1.2.x (PS/2) ------------------------ Compid Programname Release 5713aeq00 OPSYS 1.2.1 5713aew00 TCP/IP 5713afj00 DS 5713afg00 NFS 5713afe00 US 5713aet00 INed/INmail 5713afd00 Text Form.SYS 5713aez00 VS Pascal 1.1.0 5713afa00 VS Fortran 1.1.0 570603601 VS Cobol CMP 1.1.0 570603501 VS Cobol RTE 1.1.0 5713afc00 C-Compiler 5713aex00 XWindow 2.1.0 5713aer00 Whip 1.1.0 5713aey00 DOS MERGE 5713aff00 DOS ACCESS 5713aff00 DOS Server 3.3 AIX 370 -------------- Compid Programname Release 5713afl00 OPSYS 1.2.1 5713afl00 OPSYS 1.2.0 568804601 NFS 3.4 AIX 2.2.1 (RT) ---------------------- Compid Programname Release 560106103 OPSYS 2.2.1 560106203 VRM 560116501 DS 560115901 NFS 566906101 US 560119101 PC Sim 560106103 INed/INmail 560106103 Text Form.SYS. 560103801 VS Pascal 560103701 VS Fortran 566905401 Fortran 77 570602601 VS Cobol CMP 570602501 VS Cobol RTE 560106103 C-Compiler 5799DGC00 XL Fortran 560112501 XWindow 2.1.0 560118901 Whip 1.1.0 560106401 SQL 2.1.0 566905201 EM 78/79 560117901 X.25 560115701 DOS Server 570902901 Xondos 560104201 PC-RJE-PL BSC 560104301 PC-RJE-PL SNA 560104401 PC-3270-PL SNA 560104501 PC-3270-PL BSC ======================================================================== ======================================================================== >91.12.02 Table of contents: (I)91268. NetWare From IBM Patches/Fixes/Tech Info via TOOLS Disk. (I)91269. RISC SYSTEM/6000 executive overview brochure (U)91270. Compliance to PHIGS standards (U)91271. EXABYTE Tape - the story continues.... (U)91272. ISO-8859 printing in AIX 3.1.5 (U)91273. New Book about graPHIGS ======================================================================== >(I)91268. NetWare From IBM Patches/Fixes/Tech Info via TOOLS Disk. IBM announces NetWare From IBM Patches/Fixes/Tech Info via TOOLS Disk. Effective 11/12/91, these TOOLS Disks are available for file downloads. Three TOOLS Disks have been created. These disks contain information for the following areas: Database of Technical Novell Information Patches and Fixes for NetWare 386 Patches and Fixes for NetWare 286 Patches and Fixes are provided ONLY for NetWare From IBM products. These TOOLS Disk are: NWAREUTL managed by TOOLS at ATLVMIES NWARE386 managed by TOOLS at ATLVMIES NWARE286 managed by TOOLS at ATLVMIES NWAREUTL contains information on Novell Products, Technical Bulletins, Application Notes, Education offerings from Novell, and the Independent Manufacturer Support Program (IMSP) test results. NWARE386 contains patches and fixes for NetWare 386, NetWare NFS, NetWare for SAA, NetWare for MacIntosh 3.0, NetWare FTAM, and NetWare 386 clients/requesters. NWARE286 contains patches and fixes for Netware 286, NetWare Naming Service, and NetWare 286 clients/requesters. These disks are updated as new material is made available from Novell. To subscribe to these TOOLS Disks, use the following commands: TOOLS SENDTO ATLVMIES TOOLS NWAREUTL GET NWAREUTL PACKAGE TOOLS SENDTO ATLVMIES TOOLS NWARE386 GET NWARE386 PACKAGE TOOLS SENDTO ATLVMIES TOOLS NWARE286 GET NWARE286 PACKAGE To receive updates of changes to the TOOLS Disks, SUBSCRIBE to these packages. TOOLS SENDTO ATLVMIES TOOLS NWAREUTL SUBSCRIBE NWAREUTL PACKAGE TOOLS SENDTO ATLVMIES TOOLS NWARE286 SUBSCRIBE NWARE286 PACKAGE TOOLS SENDTO ATLVMIES TOOLS NWARE386 SUBSCRIBE NWARE386 PACKAGE ======================================================================== >(I)91269. RISC SYSTEM/6000 executive overview brochure November 26, 1991 Do you have a customer that is looking for the capabilities of high-performance open systems hardware, software, and services? Will they be running applications for the AIX environment? Then, they need a copy of the IBM RISC System/6000 Executive Overview brochure. The RISC System/6000 Executive Overview brochure offers your customer a comprehensive solution that integrates hardware, software, and services. This brochure introduces how IBM invented RISC technology, Performance Optimization With Enhanced RISC (POWER) architecture, and explains the values and deficiencies of UNIX that prompted IBM to devise AIX. Finally, discover the values and benefits of effectively managing the operational and maintenance challenges of this high-performance technology by using the support capabilities of IBM Services. The RISC System/6000 Executive Overview brochure (G544-6232) is now available from Mechanicsburg. For additional information on RISC System/6000 services, contact the Austin Software Services project office (8:00 AM to 5:00 PM Central Time) outside 512-823-3067 or T/L 793-3067, or you may direct your questions via PROFS on AUSVM8(RSXINFO). ======================================================================== >(U)91270. Compliance to PHIGS standards Compliance with the PHIGS standard has two aspects: functionality (as specified by ISO/IEC 9592-1:1989) and language bindings (FORTRAN - ISO/IEC 9593-1; Ada - ISO/IEC 9593-3; and C - ISO/IEC 9593-4 (not yet adopted). Functionality ------------- graPHIGS V2 provides all PHIGS functionality, with the following exceptions: - Archive functions - Modelling Clip - Incremental Spatial Search - CGM input & interpretation functions Language Bindings ---------------- As you know, FORTRAN and Ada bindings have been adopted and C is imminent. FORTRAN - as of 3/91, the graPHIGS API includes an ISO PHIGS FORTRAN binding. However, there is no formal certification process that I know of. Last I heard (late August), the US National Institute of Standards and Technology (NIST) plans to announce a validation service in 2Q/92 based on version 2 of their test suite. In general, we are conformant, with "reasonable" differences.) Ada - graPHIGS does not provide an ISO PHIGS Ada binding. C - graPHIGS does not yet provide an ISO PHIGS binding. (To my knowledge, NIST have no plans to announce a validation service for the C or Ada or C bindings.) ---------------------------------------------------------------------- The ISO PHIGS FORTRAN language binding shipped in Personal graPHIGS V2.2.0 last Nov 30, 1990 in the US. This complies with ISO/IEC 9592-1: 1989 PHIGS with these exceptions: archive, metafile, modelling clipping, and incremental spatial search functions. This was documented in the announcement letter or sales manual for V2.2.0 and is also found in the IBM graPHIGS manual -- ISO PHIGS Implementation Reference ( SC33-8118) Development is working on some of the above exceptions but they won't be available in the near term. ------------------------------------------------------------------------ ======================================================================== >(U)91271. EXABYTE Tape - the story continues.... Info: As described before it was possible to get an EXABYTE tape to work after changes were made in the file /etc/objrepos/PdAt. These changes worked until the next reboot of the system. Also it is not possible to reinstall a system because Inst./Maint. diskettes only work with IBM tapes. (Thanks to Bernhard Zeller who provided this information.) Now we have a way to create them with Exabyte support: 1) Make changes to /etc/objrepos/PdAt PdAt: uniquetype = tape/scsi/8mm attribute = dev_type >>> deflt = 5 values = 1 width = "" type = R generic = "" rep = n nls_index = 0 PdAt: uniquetype = tape/scsi/8mm attribute = model_name >>> deflt = "EXB-8500-85Qanx0" values = "" width = "" type = R generic = "" rep = s nls_index = 0 PdAt: uniquetype = tape/scsi/8mm attribute = mode_data >>> deflt = 0x000010080000000000000400 values = "" width = "" type = R generic = "" rep = s nls_index = 0 2) Make changes to /etc/objrepos/boot/PdAt * same data as above * this file is used to create the Inst./Maint. diskettes. 3) Make changes active on each reboot - mkdir /tmp/exa - cd /tmp/exa - cp /etc/objrepos/boot/mediadd.bff /tmp/exa/mediadd.save - restore -qTf ./mediadd.save > ./list - restore -qxvf ./mediadd.save * mediadd.bff is a backup format file which contains the ascii sources for the ODM database. The files are named '*.add'. - edit ./scsidev.add and make the same changes as under 1) and 2). - cat ./list backup -qivpf ./mediadd.bff - mv /tmp/exa/mediadd.bff /etc/objrepos/boot/mediadd.bff - sync;sync;sync * parts of the ODM database are also included in the boot information. We have to update the boot info. (Use 'root') - bosboot -a 4) Create new Inst./Maint. Diskettes. You should be able to boot and reinstall the system using an EXABYTE 8500 tape. 5) NOTE: I was not able to test this procedure - because I have no EXABYTE tape, please save the complete /etc/objrepos directoy first. - tar -xvf /tmp/odm /etc/objrepos - compress /tmp/odm - save the file /tmp/odm.Z Frank Kraemer ======================================================================== >(U)91272. ISO-8859 printing in AIX 3.1.5 Hi there, I've written a Printer Code Page Translation Table for printing ISO-8859 text files ('qprt -X 8859 filename'). This is not very difficult to write but it is really boring to type all that hex-stuff. If you are interested to get my program that generates the magic '/usr/lpd/pio/trans1/8859' file, get it from the TOOLS DISK in Munich: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET 8859 CBIN or from Dallas: TOOLS SENDTO DALVM41B IBMPC AIXDOC GET 8859 CBIN Download in binary and compile. Run it as root. Eric Marchal AIX-FSC IBM Belgium. ======================================================================== >(U)91273. New Book about graPHIGS A new IBM book about GraPHIGS from the Palo Alto Scientific Centre. Using the graPHIGS Programming Interface - Presentation Guide This is derived from the class Bill and Cathy gave in Munich a while back and is an excellent introduction to GraPHIGS. The order number is G320-3550. Cheers Iain ======================================================================== ======================================================================== This is what happens when IBM takes MDQ serious ;-) Schubert Symphony A certain IBM Executive was recently given a ticket for a perfomance of Schubert's Unfinished Symphony. He couldn't go, and passed on the invitation to a member of the recent MDQ-IBM Reorganization task force. The next morning the Exec asked how he enjoyed it, and instead of few plausible observations was handed a memo which read: 1. For considerable periods the four oboe players had nothing to do. the number should be reduced, and their work spread over the whole orchestra, thus eliminating peaks of inactivity. 2. All twelve violins were playing identical notes. This seems unnecessary duplication, and the staff of this section should be drastically cut. If a large volume of sound is really required this could be obtained through an electronic amplifier. 3. Much effort was absorbed in the playing of demi-semiquavers. This seems an excessive requirement, and it is recommended that all notes should round up to the nearest semiquaver. If this were done it should be possible to use trainess and low grade operators. 4. No useful purpose is served by repeating with horns the passage that has already been handled by the strings. If all such passages were eliminated, the concert would be reduced from two hours to twenty minutes. If Schubert had attended to these matters, he would probably have been able to finish his symphony after all. >91.12.12 Table of contents: (U)91274. Using A4 paper with nroff/troff (I)91275. There is a new version of the GTO part of update 2008 available (U)91276. Ordering address for the new GraPHIGS Book (U)91277. inst/maint diskettes for 1024 byte tapes + .fs.size on diskette (U)91278. Oracle Tuning Tips (U)91279. Cleaning up shared libraries ======================================================================== >(U)91274. Using A4 paper with nroff/troff N/TROFF by default uses the paper size LETTER. The following steps are needed to print on A4 paper without having to modify the n/troff source files. For n/troff documents one can set the paper size by setting registers on the commandline. For the A4 paper size this would be -rL11.5i -rW8i (it is actually 8.27 and 11.67 but laser printers have their own ways...) This should work on all texts that do not specify page sizes internally. so the n/troff command would look like: n/troff -rL11.5i -rW8i file.tr > output This does not work for macro packages like -man that have some internal defaults that do not depend on those registers. Fortunately they can be modified in one place so that adaption of individual files is not necessary. The following text should be put in /usr/lib/tmac/tmac.an right after the .so /usr/lib/macros/an command. --CUT----CUT----CUT----CUT----CUT----CUT----CUT----CUT----CUT----CUT----CUT-- ."Set Page Size Macro ."Usage: .SP line-length page-length ." * values given in inches .de SP .nr LL $1i .nr )L $2i .pl n()Lu "set page length .ll n(LLu "set line length .lt n(LLu "set tile line length .. ."Call .SP with appropriate values to set global for your system ."These are the numbers for A4 .".SP 8.27 11.67 ."Including margins for man formatting we get: .SP 7.0 11.0 --CUT----CUT----CUT----CUT----CUT----CUT----CUT----CUT----CUT----CUT----CUT-- For the 3270 impaired: is backslash Be sure to have no extra lines after the .SP command, else you get an empty header page on every document| Thanks to Tommy Chan and Ed Hill who provided the n/troff skill. ======================================================================== >(I)91275. There is a new version of the GTO part of update 2008 available Update 2008c is included now in the GTO2008 Package Get it with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET GTO2008 PACKAGE or TOOLS SENDTO DALVM41B IBMPC AIXDOC GET GTO2008 PACKAGE ======================================================================== >(U)91276. Ordering address for the new GraPHIGS Book I've found out that you can not order the book mentioned below via Mechanicsburg or Copenhagen. If you are interested you should order directly from: Palo Alto Scientific Center 1530 Page Mill Rd Palo Alto CA 94304 USA > A new IBM book about GraPHIGS from the Palo Alto Scientific Centre. > Using the graPHIGS Programming Interface - Presentation Guide > This is derived from the class Bill and Cathy gave in Munich a while > back and is an excellent introduction to GraPHIGS. The order number > is G320-3550. Sorry for the trouble some of you went to before I found this out... Cheers Iain ======================================================================== >(U)91277. inst/maint diskettes for 1024 byte tapes + .fs.size on diskette These procedures came in useful recently where we had to install tapes backed up at 1024 bytes/block, and we wanted to modify the .fs.size file to create different filesystems from those on the .fs.size file on the original tape. As an aside, it is worth checking that if you have "stacked" filesystems (e.g. /usr/ingres, and /usr/ingres/database), that they appear in /etc/filesystems, and in .fs.size in the correct "mounting' order (/usr/ingres first in this example). If not, the system will create the "lower" branches first, mount them, and then cover them up when the "higher" levels are created and mounted. Obvious in hindsight||| Now for the really useful stuff (|?|) Indulis ---------------------------------------------------------------------- Installation diskettes for 1024/byte/block tapes & .fs.size on diskette Indulis Bernsteins, IBM Perth, 10 Dec 91 ---------------------------------------------------------------------- This has been tested for 2007 level but should also work on 3005. UNIX commands are shown inside single quotes... e.g. 'cat' (don't type the single quotes!) Note that you can build a single Inst/Maint diskette which reads 1024 byte/block tapes AND reads .fs.size from diskette. Just combine the "vi" steps before you produce the new Inst/Maint diskette. How to build an Install/Maint diskette for 1024 byte/block tapes ---------------------------------------------------------------- 1) find a filesystem with 1.5 MB free (....say /tmp) 2) 'cd /tmp' 3) 'mkdir inst' 4) 'cd inst' 5) insert Installation/Maintenance diskette into drive (that's the diskette drive of course|) 6) 'restore -xv' 7) 'vi startup2' 8) search for string "block_size" (vi command is /blocksize) 9) change "block_size=512" to "block_size=1024" 10) save file and exit from vi (vi commands :w then :q) 11) insert a blank, formatted diskette into the diskette drive 12) 'find . -print backup -ivpf/dev/fd0' 13) remove the diskette and label it "Installation/Maintenance 1024 bytes/block" 14) this step left blank intentionally (it's the end|) How to build an Install/Maint which reads .fs.size from diskette ---------------------------------------------------------------- 1) find a filesystem with 1.5 MB free (....say /tmp) 2) 'cd /tmp' 3) 'mkdir inst' 4) 'cd inst' 5) insert Installation/Maintenance diskette into drive (that's the diskette drive of course|) 6) 'restore -xv' 7) 'vi ./usr/lpp/bosinst/bosmenus' (NOTE THE DOT IN THE FILENAME|||) 8) search for string "restbyname" (vi command is /restbyname) 9) change "$instdev" to "/dev/rfd0" 10) save file and exit from vi (vi commands :w then :q) 11) copy your desired .fs.size file to . (in this case /tmp/inst) 11) insert a blank, formatted diskette into the diskette drive 12) 'find . -print backup -ivpf/dev/fd0' 13) remove the diskette and label it "Installation/Maintenance: .fs.size from diskette" ======================================================================== >(U)91278. Oracle Tuning Tips Ask for upgrade 4, which supports 3.1.5 and has the performance enhancements. Oracle said the marketing folks might not know what you are talking about, but tell them you want to speak to the technical Oracle guys and they'll be able to get it for you. Just more undocumented info on Oracle... Here are the procedures and hints on the installation: 1)Use AIX 3005 (3.1.5) 2)Login as root. 3)Do a "cp /etc/inittab /etc/inittab.bak" to backup inittab. Oracle will change the inittab file during the installation. Ifthe installation is unsuccessful, /etc/inittab will be destroyed. Ifthere is no backup in the harddisk, you have to install the whole operating system again. But if the .bak file is present, you can recover by booting in maintenance mode, issue the command "etc/continue hdisk1", and then cover the .bak file. 4)Mount a journaled file system of /u/oracle and add the user oracle from SMIT. Change the group of oracle to dba. The space requires of the file system depends on how large your dataspace is, but make the file system at least 100meg. 5)Load the tape by "installp -d /dev/rmt? all". If you are reinstalling, remember to add a "-F" to installp. Otherwise, errors will occur. 6)Oracle will ask you what user and what directory you want to use. Use "oracle" as the user and "/u/oracle" as the directory. Check with Oracle as to performance in RAW mode versus filesystem. Earlier versions did not have RAW mode performing well. 7)After the tape is loaded successfully, run "./oracle.install" with root in /u/oracle/install. 8)Now, reboot the system with "shutdown -Fr". Oracle does not say you have to reboot the system, but strange errors will occur if you dont. 9)Increase your paging space now. This is not documented in oracle, but not enough paging space will give you a "kill -9" during the installation process. 10)Login as "oracle" and then run "./oracle.install" again in/u/oracle/install. It will ask you some questions concerning the database. Select the default if you don't have a hint on what they are asking. 11)After the installation is successful, change /etc/inittab. Delete the last line, and add the following 2 lines there: orapw:2:wait:/etc/loadext /etc/pw-syscall orapw:2:wait:/bin/sh /u/oracle/bin/dbstart This will allow automatic startup and shutdown of the database. 12)Change the filed from "N" to "Y" in /etc/oratab. 13)Login as user="system" and passwd="manager". The database is successfully installed at this point. Tuning and benchmarking: Here are some hints on tuning RISC System/6000 with Oracle application. differently, but here are some hints. 1)For benchmarking, you can go to sqlplus, and then "set timing on". This will give you the runtime on your application. 2)Make the SGA as big as possible, and lower the paging space now and keep the paging activity on the absolute minimum. 3)Make sure the redo-logs are on a separate drive, so the sequential write to them can be done without head movements. 4)Spread the db-files on different available disks, and use a number of db_writers at least equal to the number of drivers with db-files. Make the logical volumes with db-files onthem are on contiguous physical partitions. 5)Use iostat/vmstat to verify that the disk load is spread even among the disks. 6)Use the 4096 byte oracle blocks (db_block_size) in /u/oracle/dbs/init.ora. Default is 2048. 7)Increase other parameters in init.ora. You have to tune this to suit your particular application. 8)After you have done all these, reboot your system and login as oracle again before doing the testing or benchmarking. 9)If you are using "SELECT" from your application heavily, try to create indexes. This should be documented in the oracle user's guide. 10) Use cluster whenever possible. 11) Change the login.sql file (or make one up) to include the following parameters: SET ECHO OFF SET PAUSE OFF SET SHOW OFF SET TAB ON SET TERM OFF Stephen A. Laufer ======================================================================== >(U)91279. Cleaning up shared libraries From marcwatson.ibm.com (Marc Auslander) Newsgroups: comp.unix.aix The AIX shared library loader accumulates images of shared libraries and shared loadable programs in the shared library segment. These images will eventually migrate to paging space. In my limited experiments, a running system will normally contain about twice as many bytes of such cached libraries as are actually in use. If program development is being done on a shared library or shared loadable module, many (different) defunct copies can accumulate. /etc/slibclean issues a form of the unload system call which causes a garbage collection of the shared library segment. If either of the above phenomena are causing pressure on paging space, you should consider putting a periodic call to slibclean in (root) cron. (I have not done so on my machine, by the way). I would think that once an hour would be a good starting point. If you have done program development on shared libraries or shared loadable modules, you may have noticed that you can't write them, but must rm them to replace them. This is because, as long as they are cached, they are kept open "text busy" to prevent changes. -- Marc Auslander (IBM) (Internet) ======================================================================== ======================================================================== suit n. 1. Ugly and uncomfortable 'bussines clothing' often worn by non-hackers. Invariably worn with a 'tie', a strangulation device that partially cuts off the blood supply to the brain. It is thought that this explains much about the behaviour of suit-wearers. Compare droid. 2. A person who habitually wears suits, as distinct from a techie or hacker. See loser, burble, management, and braindamaged. English, by the way, is relatively kind; our Soviet correspondent informs us that the corresponding idiom in Russian hacker jargon is 'sovok', lit. a tool for grabbing garbage. From the New Hackers Dictionary >91.12.18 Table of contents: (U)91280. TCP/IP VM V2.2 ANNOUNCED December 11, 1991 (I)91281. RESTRUCTURING ANNOUNCED IN ADVANCED WORKSTATIONS DIVISION (C)91282. Include file changes in GL on AIX 3.2 (C)91283. AIX 3.2 GUI update class material is available on our ICTIPS disk (U)91284. Hermes: A Language for Programming Distributed Systems (U)91285. X-Station Login to a Remote Host (U)91286. AIXTIPS is on vacation until mid January ======================================================================== >(U)91280. TCP/IP VM V2.2 ANNOUNCED A new release of VM TCP/IP Version 2 was announced on 12/10/91 and will be available on 12/27/91 (announcement letter 291-701). Key new features are: - SQL/DS VM Server support, and RS/6000 and SUN Client support for data base queries from interactive sessions or applications - FDDI support using the 3172 - Network Management support for the 3172 (SNMP) - VM/ESA support - 3745 Ethernet support (hardware available 2H92) - Performance enhancements to NFS, SMTP, Domain Name Server - Simplified installation - Accounting support for NFS - Extended Sockets supports - Support for OSF/MOTIF V1.1.2 ======================================================================== >(I)91281. RESTRUCTURING ANNOUNCED IN ADVANCED WORKSTATIONS DIVISION December 5, 1991 As part of today's announced restructuring of the Personal Systems line of business, William J. Filip, IBM vice president and president, Advanced Workstations Division, has announced a restructuring to focus on five core business areas in order to better satisfy specific customer requirements. The five new areas are: -- Personal workstations, i.e., high-volume entry level workstations, including entry graphics and multimedia extensions; -- Advanced workstations and servers, i.e., high-performance technical workstations and technical/commercial workgroup servers; -- Advanced systems, i.e., high-end multi-user systems and servers, including future multiprocessor configurations; -- Graphics systems, i.e., high-performance 3D graphics-intensive workstations; -- Original equipment manufacturer (OEM) marketing and support. These businesses will be complemented by five business operations teams providing cross-unit support: -- Architecture and performance; -- Technology; -- Development operations; -- Customer support; -- Finance and business planning. In support of this restructuring announcement, Mr. Filip has announced the following changes in his organization: -- William F. Colton has been named vice president, systems development. He was vice president, graphics systems, AWD. Mr. Colton manages the advanced workstations and servers business and serves as the contact point for the personal workstations and graphics systems businesses, as well as development operations. Reporting to Mr. Colton are: Advanced workstations and servers: -- William C. Cates, manager of advanced workstation and server development; -- George W. Hobgood, manager of input/output product development and product support; -- Brooks A. Loflin, manager of product line management. Systems development staff: -- Satish Gupta, program director of graphics systems; -- Claude H. Feistel, manager of graphics architecture; -- David K. Henney, manager of staff operations; -- Wayne R. Rogers, manager of hardware assurance and quality programs. -- Phillip D. Hester, who has been named vice president, systems technology. He was director of AWD engineering center systems development, AWD. Mr. Hester manages the AWD technology team and serves as the contact point for the advanced systems business, as well as the architecture and performance team. Reporting to Mr. Hester are: Technology: -- Richard J. Gilmour, manager of OEM technology development; -- Richard H. McMaster, manager of advanced technology development; -- Rudy J. Pirovitz, manager of central electronics complex (CEC) engineering; -- Theodore G. Scardamalia Jr., manager of future systems technology; -- Thomas G. Whiteside, manager of customer design center. Named to manage business areas in addition to those directly managed by Mr. Colton and Mr. Hester are: -- W. C. (Willy) Shih, who has been named director of personal workstations. He was director of AWD engineering center product development, AWD. Reporting to Mr. Shih are: -- Gary R. Heinberg, manager of personal workstations; -- Rajan Krishnamurty, manager of personal systems graphics and multimedia. -- Robert L. Swann, who has been named director of graphics systems. He was laboratory director, Kingston Graphics Laboratory, AWD. Mr. Swann's organization remains unchanged; -- Randy D. Groves, who has been named manager of advanced systems. He was development engineering area manager. Named to manage business operations teams in addition to those directly managed by Mr. Filip and Mr. Hester are: -- John T. Hollaway, manager of development operations; -- Dairl M. Johnson, manager of systems architecture and performance. Mr. Filip serves as the contact point for finance and business planning, the OEM business and customer support: -- Alan J. Bialkowski, director of plans and controls, is responsible for finance and business planning. -- Lucian Bifano, director of AWD business development and customer support, is responsible for the OEM business and customer support. Commenting on the announcement, Mr. Filip said, "This new structure strengthens our focus on each of the key business opportunities that will fuel our growth and profitability. We're committed to building an environment of empowerment and accountability that will accelerate decision making, shorten product cycles and sharpen our focus on customer requirements." ======================================================================== >(C)91282. Include file changes in GL on AIX 3.2 Some of the types defined in /usr/include/gl.h in AIX 3.1 have been moved to /usr/lpp/GL/examples/glport.h in AIX 3.2 (which used to be somewhere else earlier on in AIX 3.1). We still don't have Golden code so this may change before release. I found that about 50% of the demo sources had to be modified to include glport.h - I guess ISVs will probably hit the same problem. Cheers Iain ======================================================================== >(C)91283. AIX 3.2 GUI update class material is available on our ICTIPS disk I have list3820 files for the AIX 3.2 GUI update class run by the ITSC in La Hulpe in November. These have lots of useful information about AIC, xdt3, Motif 1.1 etc. Note that when printed you will have a LARGE binder full of notes. Get the stuff by the following TOOLS request TOOLS SENDTO MUNIVM4 AIXTOOLS ICTIPS GET GUI32UPD PACKAGE Cheers Iain ======================================================================== >(U)91284. Hermes: A Language for Programming Distributed Systems Hermes ------ Hermes is an experimental distributed systems language developed at the IBM Watson Research Center. Hermes is a strongly typed imperative language. Hermes incorporates objects and inter-object communication. Communications can be established between any pair of objects supporting the same interface. The existance of machine boundaries between objects is not visible to the programmer. Hermes is ideal for someone who wants to teach distributed programming, experiment with distributed systems, or play with an object-oriented language. We are distributing the entire Hermes language for free, including all source for the complier and demonstration programs, to anyone who wants to use it for non-commercial purposes. It is available via anonymous ftp from software.watson.ibm.com, or via a tape which can be obtained by sending a request to hermes2watson.ibm.com. Details are below. The hermes usenet newsgroup, comp.lang.hermes, has been active for 6 months. Hermes runs on many Unix machines, including the IBM RISC System/6000, Suns, Convex, HP/9000 and NeXT. Ports to other 32-bit unix boxes should be easy since Hermes is written in C and Hermes. Hermes technology ----------------- Hermes is a very-high-level integrated language and system for implementation of large systems and distributed applications, as well as for general-purpose programming. It is an imperative, strongly typed, process-oriented language. The programmer sees a single abstract machine containing processes that communicate using calls or sends. The compiler, not the programmer, deals with the complexity of data structure layout, local and remote communication, and interaction with the operating system. As a result, Hermes programs are portable and easy to write. Some important features of Hermes are: * Process Paradigm: The process is the unit of modularity. Hermes processes are as `lightweight' as procedures in Algol-like languages, and have the same data hiding properties as `objects' in object-oriented languages. A process is an independent active entity, consisting of private data and a sequential program. Processes interact by issuing calls on `output ports' (e.g. call p(a, b) sends the callmessage (a, b) on the port p), and receiving calls on `input ports'. This model yields a simple compositional semantics. It is easy to reason about Hermes processes, since a Hermes process behaves the same `in isolation' as it does when linked up to a large system. * Tables: There is a single type constructor for homogeneous data aggregates---a relational table. Tables are a consistent abstraction for data which could be implemented as strings, arrays, linked lists, hash tables, trees, indexed files, etc. The programmer can insert and remove elements from tables, retrieve elements by content, merge two tables, and copy or extract selected subsets of a table. By providing tables, Hermes makes programming simpler and more portable, gives the compiler more freedom to provide alternative efficient data representations, and eliminates potentially dangerous explicit pointer manipulation. * Compile-time checking: Hermes is strongly typed. The use of operations with operands of the wrong type is detected at compile-time. Additionally, Hermes introduces a dataflow-based checking called typestate checking. Typestate checking detects such additional errors as failing to initialize a variable, and using a variant from the wrong case. Typestate analysis also allows the compiler to reuse storage safely and thus avoid the need for run-time garbage collection. It is a goal of Hermes to detect as many errors as possible before a process begins execution. A polymorph data type is provided as an escape to defer type and typestate checking until run-time. * Security: In many languages, a single erroneous module can bring down an entire program. Because a `program' in a systems language might include multiple users, it is important to limit the effect of programming errors. In Hermes, an erroneous process may generate incorrect output values of the correct type, or may fail to generate any output values, but it can never cause other processes to crash or violate the Hermes semantics. Hermes enforces security largely at compile-time, thanks to typestate checking. Typestate checking improves performance as well as reliability, since processes on a single machine can safely share a single hardware address space, even when these processes are acting on behalf of different users. * Dynamic Configuration: Using Hermes, programmers can create, link, and rebind processes dynamically using language primitives without the need to make system calls. Ports are first-class values in Hermes. They can be assigned to variables, stored in tables, passed in messages, etc. The port type determines the interface only, not the binding to code. The effect of replacing one port value with another is to rebind a port to a `plug-compatible' process which may have completely different code but which is guaranteed to have the expected interface. The combination of dynamics with security is valuable in implementing long-lived systems that evolve over time. * Capability-Based Access Control: In Hermes there are no global names. A process can only interact with processes for which it has been given ports. Since ports are first-class, a programmer can provide controlled access to resources by writing processes that manage the resource and giving out ports only to these processes. This provides the flexible access control found in capability-based systems. Using ports as capabilities is efficient because all the checks which are needed to assure that capabilities are not forged have been done at compile-time. Obtaining Hermes ---------------- The distribution includes complete sources, as well as pre-built executables for the following platforms: IBM RISC System/6000 running AIX v. 3.1 IBM RT/PC running BSD 4.3 Sun 3 and Sun 4 running SunOS 4.0.3 or higher NeXT machine (ported by R. Lehman and S. Strumpf of Columbia University) Convex (ported by W. Korfhage of Brooklyn Polytechnic Institute) HP 9000 Series HP-UX (ported by W. Korfhage of Brooklyn Polytechnic Institute) The software system is written in a combination of C and Hermes, and should port easily to most 32-bit Unix systems. There is no license required for non-commercial use of the software. Currently, version 0.7alpha of the Hermes prototype is available. Within the next few months, a new version, 0.8alpha, will become available. You can get the software internall off AIXTOOLS, search for HERMES PACKAGE. Use the following steps to acquire the software via ftp on the internet: 1. FTP to software.watson.ibm.com (IP address 129.34.139.5) 2. Specify user "anonymous" and enter identification information (like "user@site") to the password prompt. 2. Get and read the file /pub/README.FTP for general information on software available from this machine. 3. Get and read the file /pub/hermes/README for further instructions on acquiring and installing the Hermes system. Currently, the procedure is as follows (to obtain version 0.6alpha of the software) : 3a. Get the file /pub/hermes/0.6alpha/install-hermes. 3b. Set the FTP transfer mode to binary. 3c. Connect to /pub/hermes/0.6alpha/compressed and get all the files you find there (or a subset, if you've decided you don't need certain components after reading the /pub/hermes/README file). 3d. Exit from FTP. 3e. Set 'execute' permission for the install-hermes shell script you obtained in step 3a. (Normally this permission bit is stripped by FTP). 3f. Run the install-hermes shell script. It will ask you where to install hermes and which components you wish to install. ======================================================================== >(U)91285. X-Station Login to a Remote Host Problem: 1. Since version 1.2 of the Xstation Manager it is possible to login to a remote host. But the 'rlogin' command is not able to send environment variables to the remote host. 2. If the login fails (even to the boot host of the Xstation) the next login forgets the variables too. Result: The Variables $XSTATION and $DISPLAY are missing and the start of the X clients and the window manager on the Xstation is only possible after setting $DISPLAY manually. The Solution: Using the $TERM variable together with rlogin can be hacked into a circumvention How to fix it: We assume the login shell for all users is ksh or sh, csh users need to update their individual .cshrc files. 1. Change the expiration date of the user 'nobody' ('nobody' handles the 'rlogin') You should change the expiration date to 0 or a maximum date until the X-Station is no longer allowed to do remote logins to foreign hosts. 2. Change the configuration file /usr/lpp/x_st_mgr/bin/x_st_mgrd.cf and add '-tn xstation.Xstationname' into the aixterm command at every Xstation configuration. Example: -------- The hostname of an Xstation is 'aladin', so the aixterm command now should look like: aixterm -fn Rom14 -tn xstation.aladin -e /usr/lpp/x_st_mgr/bin/login (you may add any aixterm-command you want to customize your login window: -geometry for example) The terminalname of the login window is now: TERM=xstation.aladin 3. Change the /etc/profile (at every host that allows login from an Xstation - even the localhost) and add the following lines: if `echo $TERM cut -c1-9` = "xstation." # Login from an Xstation? ( watch the backquotes "`" |) then export XSTATION=`echo $TERM cut -c10-` # Extract Xstation name and set XSTATION variable export DISPLAY=$XSTATION:0 # Set DISPLAY variable export TERM=aixterm # Reset TERM to aixterm, so that the login window works well | fi Tips ---- 1. If this is done in /etc/profile it should be automagically for all users. Individual users then could start their specific X configuration in their $HOME/.profiles in the following way: if -n "$XSTATION" then /.xinitrc & # or whatever you want| fi = open square bracket = close square bracket 2. If you do not want to change the Xstation configuration file every time you change or add a Xstation with SMIT, you can change the file /usr/lpp/x_st_mgr/bin/x_add_trm_130 (look at the README file to see where it needs to be changed). You only have to add the aixterm command: -tn xstation.$termname and your Xstation configuration file will be updated using SMIT with the right terminalname. For example the line in the x_add_trm_130 file will now look like: . . echo " aixterm -fn Rom14 -tn xstation.$termname " >> $configfile echo " -W -e/usr/lpp/x_st_mgr/bin/login " >> $configfile . . 3. You can change the file /usr/lpp/x_st_mgr/bin/login - if you want. At the end of this file you find the line: exec/bin/login $log .... You can delete the rest after '$log', because you do not need it anymore. Have fun with your X-Station Greetings Herbert Diether AIX Zentrum R/M ======================================================================== >(U)91286. AIXTIPS is on vacation until mid January This is the last issue of AIXTIPS NEWS in 1991. We well resume service at about mid january. * Merry xmas and a happy new year| i/oi i/o oi i/o o oi i/o o o oi _________ ======================================================================== ======================================================================== ... Once you're safely in the mall, you should tie your children to you with ropes so the other shoppers won't try to buy them. Holiday shoppers have been whipped into a frenzy by months of holiday advertisements, and they will buy anything small enough to stuff into a shopping bag. If your children object to being tied, threaten to take them to see Santa Claus; that ought to shut them up. -- Dave Barry, "Christmas Shopping: A Survivor's Guide" >92.01.16 Table of contents: (C)92001. PERFORMANCE NUMBERS (C)92002. Salmon information (I)92003. What is the cost of AFS and on what machines is it available? (U)92004. HP's view of 1992...... (I)92005. Handouts DCE Workshop 1991 in German (U)92006. Public Domain NQS (I)92007. Hermes for IBM Users (C)92008. Release 3.2 support guidelines document (U)92009. Passing file descriptors between unrelated processes. (U)92010. Public Domain Software (I)92011. Demos (U)92012. AIX PS/2 V1.2.1 SUPPORTS REWRITABLE OPTICAL DRIVE ====================================================================== >(C)92001. PERFORMANCE NUMBERS Attached are the updated performance numbers for the RS/6000 family, for use in announcement material. Since these results were obtained using the latest versions of the software, most older models show improvement over previously published performance numbers. We will add this information to the final versions of the appropriate hardware EDOCs. TPC numbers are not included in this chart, because these benchmarks are still being run. Estimates from the Labs are that the TPC values will be available by announcement day. As soon as I receive them I will forward them to you. TPC numbers will be available on HONE "COMP" on announcment day or as soon after announcement day as the benchmarks are completed and certified. ======================================= IBM CONFIDENTIAL UNTIL ANNOUNCEMENT UPDATED VALUES SHOWN WITH ASTERISK (*) COLUMN 1. RISC System/6000 Family Model 220 320H 340 350 520H 530H 550 560 930 950 Configuration --------Desktop-------------Deskside---------- ---Rack-- Clock Speed (MHz) 33 25 33 41 25 33 41 50 25 41 Performance(1) *SPECmark 25.9 43.4 56.6 71.4 43.5 59.9 75.9 89.3 46.1 75.8 *SPECint 17.5 21.8 28.8 36.2 21.8 29.2 36.8 43.8 22.1 36.9 *SPECfp 33.7 68.8 88.7 112.3 68.9 96.7 123.0 143.6 75.2 122.6 -LINPACK DP 6.5 11.7 14.8 18.6 11.5 20.2 25.6 30.5 15.4 25.6 Memory Standard (MB) 16 16 16 32 16 32 64 64 32 64 Maximum (MB) 64 128 128 128 512 512 512 512 512 512 Internal Files Standard (MB) 0 400 160 160 400 400 800 800 670 1,714 Maximum (GB) 0.4 0.8 0.8 0.8 2.5 2.5 2.5 2.5 12.0 12.0 Maximum With *Expansion (GB) 4.4 8.8 8.8 8.8 26.5 26.5 26.5 26.5 53.1 53.1 Memory Slots 8 2 2 2 8 8 8 8 8 8 Adapter Slots Avail. 2 3 4 4 7 7 7 7 7 7 _____________________________________________________________________________ (1) Values shown here are the results of development-level systems. While these values should be indicative of generally-available systems, no warranties or guarantees are stated or implied by IBM. IBM recommends application-oriented testing for performance predictions and offers the above commonly reported benchmarks only as an initial indicator. Additional information on these tests are available from your IBM local Branch Office or IBM Authorized Reseller. (IBM personnel or Reseller: A notice is on NATBOARD directing you to HONE/Comp and the Dallas TOOLS disk. Copies of this data should be provided to your customers. SPECmark detailed results are included on HONE for your distribution.) SPECmark: Geometric mean of the ten SPECmark tests. AIX XL FORTRAN Version 2.2 and AIX XL C Version 1.2 compiler were used for these tests. See SPEC detailed results for specific optimization parameters used for each test. INTEGER SPECmark: Geometric mean of gcc, espresso, li and eqntott SPEC Ratios. These four tests are written in C language. FLOAT PT SPECmark: Geometric mean of spice2g6, doduc, nasa7, matrix300, fpppp and tomcatv SPEC Ratios. These six tests are written in Fortran. SPECmark is a trademark of Standard Performance Evaluation Corp. LINPACK DP: Double precision, n=100 results with AIX XL FORTRAN Version 2.2, with optimization. Units are megaflops. ====================================================================== >(C)92002. Salmon information The following information may be useful to yo - ************************* IBM CONFIDENTIAL ****************************** 7011 Model 220 uses the RISC Single Chip (RSC) processor which is a single chip implementation of the RIOS Release I Processor Architecture. It is a 15.2mm x 14.6mm CMOS2S chip packaged in a 280-pin, 36mm IMC Pin Grid Array. RSC includes: Fixed-Point Unit; Floating-Point Unit; 8KB Combined Instruction/Data Cache; Memory-Management Unit; Sequencer Unit with Microcode ROS (this unit interfaces to the external I/O unit & Gt1). POWER Gt1 Performance: The performance values shown below were measured at the adapter hardware interface and do not include software overhead. The measurements were taken using the following test definition: 2D Vectors - 10-pixel randomly oriented vectors in screen coordinates written directly to the hardware interface Gt1 Performance = 200,000 2D Vectors per second Performance differences between the 220 and 320 are due to several factors, including the following: 1. The 220 has smaller cache storage capacity; 2. The 220 has smaller I/O bandwidth; 3. The 220 has microcode implementations of some functions that are implemented in hardware on the 320. ====================================================================== >(I)92003. What is the cost of AFS and on what machines is it available? To answer your other question, AFS supports the following systems for both servers and clients: Sun SPARCstation, Sun4 and Sun3 (both 68020 and 68030); RS/6000; DECstation, VAXstation, and Microvax (all ULTRIX); HP9000 Series 300/400 and 700; NeXTstation. We strive to support the most current verson of the OS, with support for old OS versions for a reasonable period of time. All distributions are priced the same. First distribution tape (hardware/OS combination) is $3,000. Each additional tape is $1,800. File servers are priced at $1,900, or a package of three for $5,400. A site license is $36,000. At the point that a site might choose to upgrade to a site license, the cost of all tapes and servers purchased up to that time is credited towards the site license cost. We also have an NFS/AFS Translator for $3,600, unlimited use at a site. This is a tool for letting NFS machines not running AFS mount the /afs file space. It is often used for PCs. All prices given reflect educational discounts. Happy holidays, Elaine elaine@transarc.com Uwe Untermarzoner IBM Academic Information Systems InterNet: untermar@stutvm3.vnet.ibm.com BitNet: UNTERMAR@DHDIBM1 VoiceNet: ++49-711-7207-4099 FaxNet: 49-711-7207-4111 SnailNet: IBM Deutschland Lehre und Forschung Plieninger Str. 140, W-7000 Stuttgart 80, Germany ====================================================================== >(U)92004. HP's view of 1992...... found in UnixWorld 1/92' Page 78: Bill Bonin, director of open systems development at Hewlett-Packard says: ".....1992 will go down as the year the mainframe died. It was majestic in its time, defining the computer age and introducing a new lexicon to the English language. The raised floors, sealed rooms, and water coolers will become cultural icons like the tailfins of a 1950s Cadillac......" frank :-) ====================================================================== >(I)92005. Handouts DCE Workshop 1991 in German Handouts of the OSF/DCE workshop 1991 held by the AIX FSC Germany can be obtained with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET DCEWKSHP PACKAGE The workshop covers o OSF/DCE Overview o DCE/RPC o DCE/THREADS o DCE/Security o DCE/DFS o DCE/Directory Service The handouts are written in German language. The package contains a tar file of all the postscript files. Mit freundlichen Gr}~en Klaus-Thomas Schleicher ====================================================================== >(U)92006. Public Domain NQS In a former AIXTIPS was mentioned, that the public domain version of NQS could be obtained from archive.ana.edu.au. this is no longer true. to get a version i have tested, try anonymous ftp to 129.69.1.12 and look in the directory soft/aix/3.1. a doc file is also available there. enjoy and have fun. uwe untermarzoner p.s. you might also find some other long seeked PD software there :-) ====================================================================== >(I)92007. Hermes for IBM Users We have put Hermes in two places to make it more accessible to IBMers. First, we have put it on an RS/6000 at Research which is an anonymous ftp server for the IMB internet (MPN). Second, we have put it on the AIXTOOLS disk as a Hermes package. (Almost--it should show up there tonight.) To get and install Hermes from the internet anonymous ftp follow these instructions: 1. ftp to shire.watson.ibm.com. 2. Specify user "anonymous" and enter identification information (like "user@site") to the password prompt. 2. If you've ftp'ed to software.watson.ibm.com get and read the file /pub/README.FTP for general information on software available from this machine. 3. Get and read the file /pub/hermes/README for further instructions on acquiring and installing the Hermes system. As of December 1991, the procedure is as follows (to obtain version 0.7alpha of the software) : 3a. Get the file /pub/hermes/0.7alpha/install-hermes. 3b. Set the FTP transfer mode to binary. 3c. Connect to /pub/hermes/0.7alpha/compressed and get all the files you find there (or a subset, if you've decided you don't need certain components after reading the /pub/hermes/README file). 3d. Exit from FTP. 3e. Set 'execute' permission for the install-hermes shell script you obtained in step 3a. (Normally this permission bit is stripped by FTP). 3f. Run the install-hermes shell script. It will ask you where to install hermes and which components you wish to install. ftp commands: cd pub/hermes get README cd 0.7alpha get install-hermes binary cd compressed prompt mget * To get and install Hermes from the AIXTOOLS disk follow these instructions: ON VM 1. toolcat 2. aixtools 3. get package on Hermes 4. ftp to Unix system On AIX 5. make install executable 6. run install Arthur artg@watson.ibm.com ====================================================================== >(C)92008. Release 3.2 support guidelines document The support guidelines for AIX 3.2 are availabe through our confidential disk. Get it with TOOLS SENDTO MUNIVM4 AIXTOOL ICTIPS GET SUPGUIDE SCRIPT It contains the support information for Release 3.2. You are receiving this guide based on your involvement in level 2 or technical support. Please feel free to distribute this document to any IBM support personnel. Note that this document is classified IBM confidential until announcement. John S. Williams ====================================================================== >(U)92009. Passing file descriptors between unrelated processes. Hello everybody, I found this in chapter 6.10 of UNIX Network Programming written by Stevens. He provides a simple C example how to pass 'open files' or better 'open descriptors' between two unrelated processes. I ported his example to AIX (some minor changes) and did some tests. "....to pass a descriptor from one process to another, the two processes must be connected with a UNIX domain socket. The only way to pass a descriptor is for the sending process to use the sendmsg() system call and the receiving process must use the recvmsg() system call." This small example is a variant of the 'cat' command. Receive the file passfd.tar.Z It is available on our TOOLS disk via TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET PASSFD TARZ - $ uncompress passfd.tar.Z # uncompress - $ tar -xvf ./passfd.tar # unpack files - $ ls # check files readme # this file makefile # for compilation str_pipe.c # 1. Program pass_fd.c # 2. Program - $ make # create executable - $ str_pipe # run the example What's really going on: ----------------------- str_pipe # start program socketpair() create unnamed stream pipe fork() child Parent +----------+----------+ Child wait() for child exec() pass_fd program pass_fd program starts open() file sendmsg() write fd to pipe exit() - stop process recvmsg() read fd from pipe write() copy from fd to stdout exit() - stop process have fun - frank :-) :-) ====================================================================== >(U)92010. Public Domain Software ANNOUNCING THE AIX PUBLIC DOMAIN SOFTWARE LIBRARY The AIX Competency Center, operated by the UCLA School of Engineering and Applied Science (SEASnet), is pleased to announce the availability of: The AIX Library of Public Domain Software The AIX Library has been put in place to provide a centralized repository of public domain applications, tools, utilities, device drivers, scripts, and other useful software that has been developed or ported to the IBM AIX Family environment. The initial focus is the exchange of codes and ports that are running, or are in process, for the RISC System/6000. However, code that runs on mainframe AIX and AIX PS/2 will also be accepted. If your customers have applications or tools that they would like to make available to other AIX users, ....or they want to see what kind of work others have been doing on the RISC System/6000, ....the AIX Library of Public Domain Software provides a place for your customers to share with peers! Users can subscribe to this INTERNET library by opening an ftp connection to AIXPDSLIB.SEAS.UCLA.EDU at ip address 128.97.2.211. Login as 'anonymous' or as 'ftp' which will automatically put the user into a special ftp mode in a special, restricted environment. For the password, the user should use his login id and host name expressed as an INTERNET address: (e.g. CNRICKS@LSAVMIC4.VNET.IBM.COM). Once connected, the user may retrieve a set of more detailed instructions with the ftp command: get README The README file contains a list of further files of interest and general mappings which will help locate them. By retrieving the README file, users agree to abide by instructions contained therein, and in any additional files which the README file references. Support for codes, if any, will be provided by the developer or the individual responsible for the port, unless specifically stated. While the AIX Library is initially available to INTERNET users only, dial-in access will be announced Mid-January '92. Users desiring access via dial-in should watch for its announcement on this bulletin board. Questions on this notice are to be forwarded to: LSAVMIC4(CNRICKS) ====================================================================== >(I)92011. Demos INPUT FOR NEW RISC SYSTEM/6000 DEMOS AIX Marketing believes that having the right RISC System/6000 demos are a key ingredient to marketing in this product area. The Center Marketing Systems & Technical Support group that provides the AIX Floor System seems to be the best vehicle for maintaining and distributing RS/6000 and related demos to the field. AIX Marketing plans to work with the CMS&TS group to help insure that the right demos that you need are available. We can't do that effectively without your input. If you would give us feedback for some or all of the questions below, we can provide you with better tools to do your job. (Make this survey easy on yourself. The questions below represent the type of information we are looking for, but please give us your feedback in a format that is easy for you.) 1. First, do you agree that demos are important to marketing the RS/6000? If not, why? How important do you think they are? Should we be making a big investment in demos, or should we use our resources for something else? (Resources are limited.) 2. What is your familiarity with the AIX Floor System? Do you use it? Do you agree that it is the best vehicle for distribution to the field? If not, what do you propose. 3. What do you like/dislike about the current floor system? What is most useful and what is least useful? What changes, if any, would you recommend? 4. What types of new demos do you need? Keep in mind that demos that are useful to a very limited audience, are least advantageous to distribute nationally. Do you have any recommendations for this type of demo? Also, do you want demos that are oriented around a specific application? Can you learn these well enough to give a demo to a customer? 5. Are some types of demos best obtained by you individually, rather than nationally distributed? What about demos conducted in partnership with business partners? What guidance would you give us in choosing demos for distribution in light of these questions? 6. The bottom line! If you haven't already stated it, specifically, what demos do you need that are not provided today. (This is question # 4 again, but its one that we really need your input to.) Please send your feedback as soon as possible to: Frank Caldarola at AUSVM6(FRANKC). Thank you for helping us better determine where to invest our resources. ====================================================================== >(U)92012. AIX PS/2 V1.2.1 SUPPORTS REWRITABLE OPTICAL DRIVE With the installation of PTF U401545, service level 1010, AIX PS/2 v1.2.1 provides support for the Personal System/2 3.5-inch rewritable optical drive (#0162, 6450162). This technologically advanced SCSI storage device features high performance (4.3MB/second data transfer rate, 66ms average seek time) and high capacity (127 million bytes formatted) in a compact 3.5-inch half-high package. For additional information about the rewritable optical drive, see ALET 191-082 dated 06/11/91. To order PTF U401545, service level 1010, contact IBM Software Defect Support at 1-800-237-5511. ====================================================================== >(I)92013. Getting some sense out of sense data dsense is a c language program designed to look up sense byte information found in the output of certain hardware errors as displayed by the errpt -a command of a Risc System/6000 running AIX. Get it from AIXTOOLS as DSENSE PACKAGE (use TOOLCAT AIX) ====================================================================== ====================================================================== Memo to: FILE Subject: Special Calendar for "RUSH JOBS" MIR FRI FRI FRI THUR WED TUE ========================================================= 8 7 6 5 4 3 2 16 14 13 12 11 10 9 23 22 21 20 19 18 17 32 29 28 27 26 25 24 39 38 37 36 35 34 33 ========================================================= * This is a special calendar which has been developed for handling rush jobs. * All rush jobs are required yesterday. With this calendar you can order your work on the 22nd and have it delivered on the 18th. * Everybody wants his job by Friday, so there are THREE Fridays in every week. * There are EIGHT new days at the end of the month for those end-of-the-month jobs. * There is no 1st of the month, so there cannot be late delivery of end-of-the-month jobs on the 1st. * MIRDAY is a special day each week for performing miracles. >92.02.03 Table of contents: (U)92026. QSTAR (TM) OPTICAL STORAGE SUBSYSTEMS FOR AIX ON THE /6000 (U)92027. PERCEPTICS CORP.'S OPTICAL STORAGE FOR AIX ON THE RISC SYSTEM/6000 (U)92028. DIGIBOARD DIGICHANNEL C/X SYSTEM FOR RISC SYSTEM/6000 (U)92029. Another REWRITABLE OPTICAL DISK FOR RISC System/6000 (I)92030. Client Server Demonstrations (I)92031. Problem with RISC/6000 SCSI Microcode fix (I)92032. FAQ release 8 for aix 3.1 formatted for a 3820 (U)92033. "on" - DISABLE IT NOW ||| (U)92034. moveOpaque option on AIX 3.2 Motif Window Manager (U)92035. PCSIM within AIX Shell script (I)92036. AIX SDE Workbench demo available on AIXTOOLS (I)92037. Internal Distribution of WorkBench/6000 and Integrator/6000 (I)92038. Remote printing MVS: MVS LPR/LPD is coming| (U)92039. LED Codes on the /6000 (U)92040. A Modem Setup Guide ====================================================================== >(U)92026. QSTAR (TM) OPTICAL STORAGE SUBSYSTEMS FOR AIX ON THE /6000 January 22, 1992 QStar Technologies, Inc. markets fully integrated WORM (Write Once Read Many), rewritable and multifunction optical drives and jukeboxes for RISC System/6000 platforms (AIX-based). Supporting more than 1000 sites worldwide, all QStar subsystems incorporate a consistent product development criteria: Clean, plug-and-play integration to AIX environments. Complete application transparency. NFS compatibility. Modular design for system upgradability. Platter-specific, on-disk directory information. QStar high capacity WORM, rewritable and multifunction optical storage subsystems are manufactured by such optical drive and jukebox vendors as Sony, Hewlett Packard and NKK America. A wide range of capacities to meet specific customer needs are provided: QStar 12" WORM W Series: QStar W6G - up to 6.55 Gbytes of storage, single drive with controller, optical file system (OFS (TM)); $32,500 list price. QStar W328G - up to 328 Gbytes of storage, two drives, contains up to 50 shelves, ViewStore jukebox management software; $179,995 list price. QStar 5.25" Rewritable and Multifunction Series: QStar R650M and M650 - up to 600Mbytes of storage, single drive with controller, optical file system; $5,495 and $7,495 respectively. QStar R10G and M10G - up to 10Gbytes of storage, single drive, 16 shelves, ViewStore jukebox management software; $24,995 and $29,995 respectively. QStar R20G and M20G - up to 20Gbytes of storage, two drives, 32 shelves, ViewStore jukebox management software; $44,995 and $49,995 respectively. QStar R35G and M35G - up to 35Gbytes of storage, two drives, 56 shelves, ViewStore jukebox management software; $56,495 and $59,495 respectively. QStar R57G and M57G - up to 57Gbytes of storage, two drives, 88 shelves, ViewStore jukebox management software; $74,495 and $79,495 respectively. QStar R93G and M93G - up to 93Gbytes of storage, two drives, 144 shelves, ViewStore jukebox management software; $104,495 and $109,495 respectively. Vendor contact: Mr. Williams J Conners, Jr. QStar Technologies, Inc. 6707 Democracy Blvd. Suite 202 Bethesda, MD 20817 (301) 762-9800 FAX: (301) 762-9829 Internet: INFO QSTAR.COM ====================================================================== >(U)92027. PERCEPTICS CORP.'S OPTICAL STORAGE FOR AIX ON THE RISC SYSTEM/6000 January 22, 1992 Perceptics Corporation, a subsidiary of Westinghouse, is an integrator of optical disk storage subsystems for the RISC System/6000 computer (AIX-based). A complete array of subsystems are available including LaserSystem (TM) (stand-alone subsystems configured with either 5.25", 12" or 14" optical disk drives), or LaserStar (TM) (jukebox or autochanger subsystem with the same complement of optical disk drives). LaserSystem includes an optical disk drive, which features Write Once Read Many (WORM) or Rewritable (Magneto-Optical (MO) or erasable) technologies, cables, rack-mounting hardware and Perceptics' LaserWare (TM) file system software. The LaserWare file system software transparently emulates a standard magnetic disk device such that system utilities and application software do not have to be modified in order to use the optical disk (WORM or Rewritable). Media, installation and complete on-site maintenance services are available for each system. LaserStar is a complete optical disk jukebox subsystem based upon Perceptics' LaserWare optical disk file system software and is fully compatible with the LaserSystem stand-alone optical disk subsystem. The jukebox software allows the operating system to view the jukebox as multiple disk drives, where each disk drive corresponds to to a media surface in the jukebox. LaserStar provides automatic, transparent access to the massive storage capacities of optical disk jukeboxes which range from 30 gigabytes to over 1 tetrabyte in a single subsystem. A typical optical disk jukebox subsystem consists of a robotic disk handling mechanism, one or more media (optical disks) storage units, one or more optical disk drives, cables and LaserStar jukebox software. Media, installation and on-site maintenance services are also provided with each jukebox. Vendor contact information Mr. Robert Koecheler Perceptics Corp. 725 Pellissippi Parkway Knoxville, TN 37922 (800) 448-8544 ====================================================================== >(U)92028. DIGIBOARD DIGICHANNEL C/X SYSTEM FOR RISC SYSTEM/6000 January 22, 1992 Digiboard is a leading supplier of connectivity products for multiuser computer systems. Their DigiChannel C/X System is a serial I/O subsystem which significantly expands the maximum number of EIA-232 devices (terminals, modems, etc.) that can be attached to the RISC System/6000. The DigiChannel C/X System consists of an adapter card, which occupies a single Micro Channel slot, and up to eight intelligent 16-port concentrator boxes. Two synchronous EIA-422 channels link the adapter to two concentrator boxes. Three additional concentrator boxes can be daisy chained to each original concentrator, providing the flexibility to attach up to 128 EIA-232 devices. A maximum of 7 adapter cards can be installed in a RISC System/6000, depending on slot availability, facilitating the attachment of up to 896 EIA-232 devices per system. The intelligent 16-port concentrator boxes (up to 8 per adapter card) can be wired up to 1000 feet away from the RISC System/6000 or can be many miles away through the use of synchronous modems. This brings additional configuration flexibility to installations where users are concentrated in different locations in a building or across the country. DigiBoard has been approved to participate as a hardware vendor in the Software Solutions Program under Cooperative Programs. The Software Solutions Program was developed in response to requests from IBM Marketing for offerings from vendors who have solutions that can benefit from IBM Industry support and positioning. IBM representatives can reference sell the vendor's solution. This product comes with a 5 year Digiboard warranty and DigiBoard provides free technical support via an 800 number. IBM does not provide warranty service on this product. The terms and conditions of warranty service are between the customer and DigiBoard. A customer that desires IBM maintenance service for this product can purchase a special bid for maintenance from IBM Service. In this case, the responsibility of obtaining replacement parts and the resolution of warranty issues remain between the customer and DigiBoard. For application, product, or general marketing information, contact: Alan Ainsworth, Digiboard, at 612-943-9020. ====================================================================== >(U)92029. Another REWRITABLE OPTICAL DISK FOR RISC System/6000 January 22, 1992 Does your customer have a requirement for high capacity data storage? Then you should be aware of ALPHATRONIX rewritable optical storage solutions for the RISC System/6000. Consider these features: * Configurations from 650MB subsystem to 93.6GB jukeboxes. * No Need to install another device driver....uses std AIX sc driver. * Appears to RS/6000 as a standard AIX Journaled File System. * This file system is "bootable". * Fully exportable and mountable as NFS volumes for read/write access. CONTACTS FOR MORE INFORMATION: IBM Joe Bivins at Dallas National Engineering Scientific Support Center - (214) 406-7578; 8-752-7578; DFWVM04(BIVINS) NSC listing swappl w/search words ALPHATRONIX and RS/6000 ALPHATRONIX John Donnee (919) 544-0001 FAX (919) 544-4079 ====================================================================== >(I)92030. Client Server Demonstrations ITSC FLASH -------- International Technical Support Center - San Jose Title: Client Server Demonstrations Audience: This announcement is being sent to all appropriate country, unit, and headquarters personnel. Date: January 22, 1992 From: Brett Paskin To: ITSC Distribution List B, Support Areas: DS, AD, PS and AX Attached is an extract from a recent note circulated by Bob Yelavich, of the Dallas Systems Center, which announces the availability of a comprehensive set of client/server demonstrations, which have been made available on the MKTTOOLS conference disk, as COOPDEMO PACKAGE. The source code can be made available to customers, in order to help them develop client/server applications. ---------------------------------------------------------------------- COOPDEMO - A Set of Cooperative Processing Applications ------------------------------------------------------- Overview This MKTTOOLS package contains a set of coordinated packages which provide demonstrations of client/server (cooperative) processing. The set is coordinated because all the packages support the same application whose function and data base are divided between two systems. Several choices are available for the two systems. The available choices for the client and server may be mixed and matched in any combination. Currently, the client can be an OS/2 EE application, CICS/ESA or CICS OS/2 transaction, AS/400 application, or AIX X/WINDOW-MOTIF application. The server (or back-end) can be an OS/2 EE application, CICS/ESA or CICS OS/2 transaction, IMS/ESA transaction, VM/SP (Release 6) or VM/ESA application, MVS/VTAM application, AS/400 application, or AIX application. All source for the applications is included. Not only is this a demonstration application, but the application documents and source code may be given to customers as a learning tool or demonstration. This can help IBM customers advance into the new area of cooperative and/or distributed applications. If diskettes are provided to IBM customers, the appropriate copyright labels MUST be affixed to the diskette. Each package contains the information needed to create the appropriate diskette label. APPLICATION DESCRIPTION The sample application performs a Part Inquiry and Part Order function. A local parts data base (which is read only) and a remote parts data base (which is updated) are used by the client to perform its function. The local data base can be on the client system or if a work station LAN is used, on a common data base server. The local data base is used for data entry validation and part description browse function. The remote data base contains the full part pricing information and availability. When orders are placed, the remote data base is updated to reflect the new part quantities available. The application also uses a local customer data base and a remote customer data base. The local data base is used for customer number verification and the remote data base provides full customer data such as shipping and billing information. The intent is to provide a working example of a cooperative application focusing on the communication aspects of the problem. Also demonstrated is the extensive connectivity between IBM platforms using a SNA LU6.2 network. The application has been designed to allow any client to use any server. The applications have been implemented in the "natural" language for their environment. When available, CPIC has been used for the communication API. On the OS/2 work station, the panels presented are managed by the OS/2 Dialog Manager and comply with CUA Graphical Model for work stations to the extent allowed by the Dialog Manager. Work station data files are managed by the OS/2 Data Base Manager. The host client uses the CUA Entry Model to the extent allowed by the supporting device standards accepted for the environment. Host server data is managed by an operating system facility such as VSAM, flat files, or data base systems. The diverse server file architectures, operating system environments, and source languages were deliberately used to demonstrate the flexibility of the cooperative solution. Regardless of the server used, the end user interaction remains the same and the client application has no knowledge of the server environment. ---------------------------------------------------------------------- Brett Paskin International Technical Support Center, San Jose VNET: PASKIN at SJSVM28 ====================================================================== >(I)92031. Problem with RISC/6000 SCSI Microcode fix ITSC is distributing this note so that WT countries are aware of an urgent problem with a fix recently sent to all RISC/6000 customers. SEs should tell their customers NOT to install this fix. Queries about this should be sent via country Support organisations to the Change Team, by the normal defect channel, NOT to ITSC ITSC Austin 31 Jan 92 ------------------------------------------------------------------------ Subject: SCSI MICROCODE INSTALL PROBLEMS (ECA039) It looks like after installing the microcode using Installp, the system does NOT reboot, because something get corrupted. The SCSI microcode in subject has been sent out to all customers world wide for correcting a problem with the SCSI I/O controller when doing a READ from tape that has variable lenght records.. I do not know at this time when and if the EMEA and other geographies customers have got the EC... I hope this time the delay in shipping is helping us.. Please advice everybody in EMEA and world trade (SE's, marketing, FSCs etc.) to check with their customers if the microcode diskette/s has arrived. If yes, they should tell the customer to NOT install it|||| Several US customers have already installed it and they can't use their system anymore||| There is a provisional recovery procedure which is attached below. Thanks, Paolo ------------------------------- Referenced Note --------------------------- Some customers have encountered DEAD machines after attempting to install ECA039 with diskettes shipped from Boulder SW distribution. Two symptoms reported are LED 552 and LED 201 when attempting to reboot the system after microcode installation. ---------------------------------------------------------------------- Possible workaround 31 Jan 92 Probable workaround for boot failure LEDs 201, 299, or 552 due to the applying a SCSI I/O controller microcode diskette. Warning: This workaround is only known to be valid for above leds resulting directly from the installing of the SCSI I/O controller microcode diskette that begain shipping to customer in January 1992. The SCSI I/O controller microcode diskettes distributed prior to January 1992 do not cause any problems. IBM currently has stopped shippment of the bad diskettes and are working to correct the problem and begin reshippment. The stop ship occurred on January 30th 1992. The failing diskettes were shipped with a READ ME document numbered ERRLTR190B. LED 552 recovery o Boot from removable installation media (bootable tape or boot diskettes) o Choose item 5 "Perform System Maintenance" from Install/Maint menu. o Execute: /etc/continue hdisk? Where hdisk? is the hard disk that contains your boot logical volume. This is usually hdisk0 . o Execute: exit This will allow you access to the ram file system. o Execute: /bin/cp -p /mnt/etc/methods/cfghscsi /mnt/etc/methods/cfghscsi. o Execute: /bin/cp -p /etc/methods/cfghscsi /mnt/etc/methods/cfghscsi o Execute: /mnt/bin/chroot /mnt /bin/ksh o Execute: df /tmp Make sure you have at least 7.5MBs o free space in /tmp. If not, then remove files from /tmp until you do have the space. o Execute: bosboot -a o Execute: savebase -v o Execute: sync o Reboot in normal mode. You should come up fine. If not, contact your Support Centre to request assistance. page 2 of 2 LED 201 or 299 These leds appear to indicate that, in this case, your NVRAM has been corrupted. o Power down your system. o Put key in service mode. o Using your hardware Installation/Service guide to locate your battery, disconnect the battery from the system. o Leave battery disconnect for 30 minutes. o Reconnect battery o Insert your removable installation media (bootable tape or boot diskettes o Power up in service mode If you couldn't already, you should now be able to boot from your installati media. o Continue with steps under LED 552 ====================================================================== >(I)92032. FAQ release 8 for aix 3.1 formatted for a 3820 I formatted the FAQ (frequently asked question) on AIX 3.1 as a script/list3820 document to be printed on 3820 printers. The faq list is distributed on the Internet and maintained from B. Engsig (Oracle). Before printing please unTERS the file and remane it to FAQ LIST3820. Get it from the internal TOOLS disk with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXFAQ TERS3820 or TOOLS SENDTO DALVM41B IBMPC AIXDOC GET AIXFAQ TERS3820 have fun --frank ====================================================================== >(U)92033. "on" - DISABLE IT NOW ||| On comp.unix.aix was a discussion about the "on" command and its potential as a security hole. IBM ships the necessary deamons enabled by default in AIX 3.1, not a very good thing. In AIX 3.2 the "on" command as well as some similar utilities will be shipped disabled by default. Meanwhile disbale rpc.rexd by commenting the appropriate line in /etc/services or use the securetcpip command for strong IP security. afx The following is from SECURITY FORUM on IBMUNIX and explaines the problem: In my /etc/inetd.conf, I find TWO entries: exec stream tcp nowait root /etc/rexecd rexecd rexd sunrpc_tcp tcp wait root /usr/etc/rpc.rexd rexd 100017 1 I thought all the time that the current discussion was about 'rpc.rexd' and the other 'sunrcp' stuff, not about 'rexecd'. Unlike 'rshd' and 'rlogind', 'rexecd' ALWAYS asks for your password (which might be taken from your .netrc), so it is not clear why it should have a problem. A quick test showed me that commenting out 'rpc.rexd' disabled 'on', while commenting out 'rexecd' had no effect. Playing a little with 'on' I have to say that the associated authentication is EXTREMELY POOR. Since I don't believe in 'security by obscurity', I will tell you about it: 'on'/'rpc.rexd' does neither ask for a password, nor for an entry in hosts.equiv, nor for an entry in .rhosts. I does not even check for the login shell defined for the user on the remote host. It just sets up an environment with all your local variables and then runs exec..() on the command you typed. It also fails to check whether the userid is expired (as does rshd, by the way). The only thing that causes a little problem is that it wants to mount your current directory from you current host, but it is sufficient that you just export it. You cannot become 'root' via 'on', but just guess what you can do as 'bin' | SO THERE IS ONLY ONE RECOMMENDATION: DISABLE THE THING ||| Michael Niksch ====================================================================== >(U)92034. moveOpaque option on AIX 3.2 Motif Window Manager For those of you that like to be particularly brutal to your RISC System/6000, you can turn on the "moveOpaque" option to the mwm. Requires AIX 3.2, of course. Just place Mwm*moveOpaque: True in your .Xdefaults or your Mwm resource file, and you get a nice effect. Too bad it's not documented anywhere I can find. Mickey Coggins -mcog at chvm1 ====================================================================== >(U)92035. PCSIM within AIX Shell script We've been successful in initiating a PCSIM process, executing a specific set of DOS tasks, then killing the process -- all within control of AIX shell scripts. The following two listings are the two scripts used. Notes: - The delay built into PCBATCH.CAN is there because attempts at an immediate "kill" caused shells to hang up. - The '/usr/lpp/ice/sys/pcsim/Ddrive/PCSIM.DUN' file is the "go" file mentioned in the second referenced Append. Many thanks to John Dlugosz and to Jim Cox in the 'AIX Strategy and External Relations' group, Austin. PCBATCH.SH -- ############################################################################## # # # Utility to copy an AIX text file, passed as the only argument, into # # a DOS file within a shared directory, DOS/TERSE the file, and backup # # the tersed file to diskette(s). # # # # Syntax: pcbatch.sh pathname # # where: pathname is that of the file to be TERSEd # # and DOS backed-up. # # # # # ############################################################################## aix2dos $1 /usr/lpp/ice/sys/pcsim/Ddrive/FILE2TRS print "cls">pcbatch print "c:utilityterse d:file2trs d:file2trs.trs">>pcbatch print "echo ....">>pcbatch print "echo ....">>pcbatch print "echo ....">>pcbatch print "pause">>pcbatch print "cls">>pcbatch print "c:dos33backup d:file2trs.trs a:">>pcbatch print "del d:file2trs">>pcbatch print "del d:file2trs.trs">>pcbatch print "cls">>pcbatch aix2dos pcbatch /usr/lpp/ice/sys/pcsim/Ddrive/PCBATCH.XXX /bin/ksh pcbatch.can & pcsim rm pcbatch PCBATCH.CAN -- ############################################################################## # # # Utility to kill the running PCSIM process once a specific file becomes # # existent within the shared directory. # # # # Syntax: /bin/ksh pcbatch.can & # # # # # ############################################################################## while ! -f /usr/lpp/ice/sys/pcsim/Ddrive/PCSIM.DUN do let i=0 done ps -ef | grep '/pcsim/' | read tk0 procid tkrest while (( $i < 50 )) do let i=$i+1 done kill $procid rm /usr/lpp/ice/sys/pcsim/Ddrive/PCSIM.DUN ........................ Regards, George Quartell ====================================================================== >(I)92036. AIX SDE Workbench demo available on AIXTOOLS AIXTOOLS: Information: WBDEMO PACKAGE created by PALANGIE at LGEVMXA. AIX SDE Workbench/6000 Demontrations and Tutorials ====================================================================== >(I)92037. Internal Distribution of WorkBench/6000 and Integrator/6000 To: Internal Users of WorkBench SDE WorkBench/6000 (Program 5696-037) and SDE Integrator/6000 (Program 5696-137) have been announced. There has been considerable interest shown in obtaining pre-release copies of these products. The steps involved in obtaining early versions of the software will be outlined here. 1a) Obtain the AIX3.2 GOLD driver + AIXWindows 1.2 (you are on your own here) WorkBench DOES NOT NOT RUN ON AIX 3.1 !!!! 1b) Request AIXWKBCH package from AIXTOOLS disk 2) You will receive a form to fill out. Fill in all the appropriate fields, paying particular attention to the 'Justification' and 'License type'. 3) Send the completed form to wying@torolab5.vnet.ibm.com or WYING @ TOROLAB5. 4) Your subscription requests will be handled on a PRIORITY basis depending on the urgency of the requirement and the number of users being served by the subscription. We are forced to do this because of limited resources. HARDCOPY DOCUMENTATION IS AVAILABLE FOR SITE LICENSES ONLY. ******************* WorkBench Request Form ********************** Request SDE WorkBench/6000 v1.1 Binary License on AIX 3.2 by AIX CASE Products By filling in the user information on the bottom of this file, you will request one pre-release copy of the WorkBench and Integrator products. In return you must agree not to copy these products except to: o move it to your machine and to maintain reasonable backup OR o if you are requesting a site license and need to propagate it on an as-needed basis This software is not officially supported as yet. All installation questions, and usage problems or bugs on AIXWKBCH FORUM on IBMUNIX disk. Have fun || Wendell Ying. ====================================================================== >(I)92038. Remote printing MVS: MVS LPR/LPD is coming| TCPIP FORUM appended at 17:15:36 on 92/01/31 GMT (by RUBIN at YKTVMV) I announced to the external IBMTCP-L mailing list that I would be making a copy of MVS LPR/LPD available internally today, with distribution to customers allowed. Unfortunately, I was out of the office yesterday and want to update the package before everyone gets a copy. So, if you are interested in obtaining a copy of this code for you or your customer, please issue: TOOLS SENDTO RALVMM TCPCONF TCPPUBS SUBSCRIBE MVSLPD PACKAGE so you can receive a copy of it when I replace and unhide it. Please note that this code will not be supported by the IBM Support Center. We are making it available in this fashion because so many people want the code, and due to packaging issues it does not appear likely that we will be able to ship it as a PTF for the V2R1 release. Bill Rubin ====================================================================== >(U)92039. LED Codes on the /6000 Another good one from the internet (comp.unix.aix). The text is a lot more than 80 columns wide at the end| >From richardkunikpok.UUCP (Richard A. Hasting Jr) Newsgroups: comp.unix.aix Subject: LED 552 INFO Date: 28 Jan 92 19:56:54 GMT Organization: Kunikpok Kennels & Komputers I got over a dozen requests for this, and since I would prefer that everyone have _ALL_ the facts, I will post this. I have seen an awful lot of misinformation, and some good and poor assumptions on what causes the machine to fail on booting up with whatever LED codes. The Table of contents are as follows LED 201 LED 223-229 LED 551 LED 552 LED 553 LED C99 LED C31 Article on using /etc/continue from the bosboot diskettes and bootable tapes Print it out because you won't be able to get to it when you need it otherwise. Changed 12/03/91 LED 201 Procedures verified on AIX 3.1.5 If a 6000 stops at led 201 during boot it may be due to either a software problem or a hardware problem. Most likely a software problem. If the leds first go past 299, and then back to 201 -- it's most likely a corrupted boot logical volume (a software problem). If the leds never get to 299 - it can't be software because the boot process hasn't yet loaded any software, so it's time to suspect hardware. Resolution to SOFTWARE problem: The corruption of the boot logical volume will usually occur if the /(root) or /tmp filesystems are full when the bosboot command is run. Bosboot is run during installation of updates. The following procedure can be used to correct this problem. - With the key in the 'SERVICE' position, boot from your installation media - Select option 5 from the installation menu - Type the following commands to vary on the root volume group /etc/continue hdisk0 - Correct the out of space condition Use 'df' to check for free space in /dev/hd4 and /dev/hd3. Erase files as necessary to correct the problem. - Create the new boot image. bosboot -a -d /dev/hdisk0 - Place the key in 'NORMAL', execute the following command shutdown -Fr Resolution to HARDWARE problem: The hardware problem of the led 201 is commonly due to a hardware problem with the system planar. The hardware issued a check stop error during boot because of a detected hardware problem. Usually the error log will contain an entry for the check stop. You should go ahead and try the software procedures just in case but be prepared to have a CE brought into the picture. The CE should contact L2 hardware support. The hardware guys are supposed to be aware of the problem. LED 223 - 229 1. boot in service mode off bosboot diskettes 2. choose option 5 3. run /etc/continue hdisk0 4. run bootlist -m normal hdisk0 5. reboot in normal mode with the "shutdown -Fr" command June 13, 1991 LED 551 SYSTEM RECOVERY There are several reasons for an LED 551: PROBLEM Solution _____________________________________________________________________________ /dev missing, or corrupted - mkdir /dev /bin empty or missing - reinstall bad boot logical volume - bosboot -a /etc problems - restore selective files if possible, or reinstall corrupted filesystems - fsck /dev/hd4 as per LED552 a bad install of the system - install AIX properly ********************************************************************** LED 552 SYSTEM RECOVERY There are, so far, several known causes, of the 552 LED upon IPL. One is bad savebase information. The second is the the log logical volume (hd8) has somehow gotten corrupted. The third is that the odm may be corrupted. To diagnose and fix a 552, I recommend these not always so simple steps: 1) Boot from bosboot diskette or tape and get to install/maint menu - Key in service position 2) choose option 5 3) run "/etc/continue hdisk#" - Check out the article on "running /etc/continue" 4) If there are any mounted filesystems (whether /etc/continue ran cleanly or not) unmount them. To check for mounted filesystems, issue the following command. # mount If /dev/ram0 is the only mounted filesystem, then goto step 5. If /dev/hd4 is mounted onto /mnt then # umount all # mount If /dev/hd4 is still mounted, then execute the following instructions # exit; # umount all # mount (The only mounted filesystem should be /dev/ram0 on /) 5) Now run fsck on the following filesystems: # fsck -y /dev/hd1 # fsck -y /dev/hd2 # fsck -y /dev/hd3 # fsck -y /dev/hd4 If this fails, or the logredo process fails, or indicates any filesystems with unknown log record type then go to step 6, else go to step 7. 6) run "/etc/aix/logform /dev/hd8" Answer YES to the question asking if you want to destroy your LOG. Logform will reformat the log logical volume. repeat step 5. 7) reboot - Key in normal position 8) If LED 552 still persists, then repeat steps 1-3, and make certain that you have chosen the proper drive that has hd5 on it. Then, goto Step 9. 9) execute the # mount command, and you should have /dev/ram0, /dev, /dev/hd4, /dev/hd2 and /dev/hd3 all mounted. If they are all there, goto step 10. If not, then run # fsck -y /dev/hd# where # is the number that matches the missing filesystem. If it gives you an error message that it could not read block 8, then the filesystem is most likly unrecoverable. If you get a bad argument error, then run # dd count=1 bs=4k skip=31 seek=1 < /dev/hdN > /dev/hdM where N is a working logical volume number, and N is the LV that fsck is failing on. then run # fsck /dev/hd# again. if it still fails, then that filesystem is unrecoverable, and needs to be recreated. hd2 and hd3 can be recreated, hd4 will require a reinstall. If hd3 is missing, then run * # lsvg -l rootvg * NOTE the number of PP's on the /dev/hd3 *# rmlv -f /dev/hd3 *# mklv -y'hd3' rootvg N * (N is the number of PP's in the Logical volume) If hd2 is the volume missing then you will need to have a backup of /usr handy. run %# lsvg -l rootvg % NOTE the number of PP's on the /dev/hd2 *# rmlv -f /dev/hd2 *# mklv -y'hd3' rootvg N * (N is the number of PP's in the Logical volume) *# mount /dev/hd2 /usr *# restore -xvdf/dev/rmt0 ./usr * (This assumes that there are no filesystems under /usr. Your milage may * differ) If /dev/hd4 has the bad super block, then you will need to install AIX on that system again. 10) set the TERM variable to the proper terminal type for your console. # export TERM=hft (or ibm3151 or vt100... whatever you happen to be running) Using your favorite editor, modify the /etc/rc.boot4 file. Change # bring up the root volume group /etc/ipl_varyon -v if $? |= 0 then while : do showled 0x552 done fi ----- TO # bring up the root volume group /etc/ipl_varyon -v RC=$? if $RC |= 0 then while : do showled 0x552 sleep 1 showled $RC sleep 1 done fi 11) Save the file, and run # bosboot -a 12) Next, if you don't have a lot of system configuration (tty's really), then run # mkdir /etc/objrepos/bak # cp /etc/objrepos/Cu* /etc/objrepos/bak # cp /etc/objrepos/boot/Cu* /etc/objrepos # savebase 13) Reboot in Normal mode again. 14) If LED 552 persists you should also have the return code from ipl_varyon in the LED. If that value is 2, 3, 4, 8, or 9 and you did not perform step #12, then do so. If you get a value of 6, 7, 8, or C, then go to step 15 If you get a value of A, then check /etc/drivers/hd_pin because it cannot be loaded. If the value is B, then the IPL record is bad, and this may be unrecoverable, we haven't figured out how to fix that one yet. Call us up, and we'll work on it with you. It is caused by an invalid IPL record on the volume group. 15) You got here because ipl_varyon failed to either open, or modify the /dev/ipldevice entry. This may be due to a bad boot LV, or because of a bad ODM. Most likly, it is a problem with the ODM. Perform step 12, if you haven't yet done so. ********************************************************************** LED 553 The system will stop during IPL with 553 in the LEDs if init has a problem running or in reading the inittab file. This will often occur when the /tmp or the / filesystem is full. The following procedure can be used to correct this problem. - With the key in the 'SERVICE' position, boot from your installation media - Select option 5 from the installation menu - Type the following command to vary on the root volume group /etc/continue hdisk0 - check for and correct an out of space condition Use 'df' to check for free space in /dev/hd4 and /dev/hd3. Erase files as necessary to correct the problem. Suspect /smit.log and /smit.script as being the problem. - Check the /etc/inittab for corruption: Usually it will be empty, or missing or have an entry in it that is not correct: - If inittab is corrupted then do the following: - Create the /etc/inittab file using your favorite editor. You must set your TERM environment variable using commands similar to the following prior to starting the editor. # export TERM=hft - if the inittab file was ok, then check the following files for any modification or permissions problem: /etc/environment /bin/sh /bin/bsh /etc/fsck missing or corrupted. This can be copied from the ram filesystem /etc/brc /etc/profile /.profile - Place the key in 'NORMAL', execute the following command shutdown -Fr Sample inittab : (#)inittab 1.22 com/cfg/etc,3.1,9021 4/6/90 17:18:07 init:2:initdefault: brc::sysinit:/etc/brc >/dev/console 2>&1 # Phase 2 of system boot rc:2:wait:/etc/rc > /dev/console 2>&1 # Multi-User checks srcmstr:2:respawn:/etc/srcmstr # System Resource Controller rctcpip:2:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons cons:0123456789:respawn:/etc/getty /dev/console piobe:2:once:/bin/rm -f /usr/lpd/pio/flags/* # Clean up printer flags files cron:2:respawn:/etc/cron qdaemon:2:once:/bin/startsrc -sqdaemon writesrv:2:once:/bin/startsrc -swritesrv LED C99 The LED C99 is usually caused by a bad /usr/bin/odmget command. /usr may be missing, or the /etc/filesystems file may be corrupted. 1) Boot from bosboot diskette or tape and get to install/maint menu - Key in service position 2) choose option 5 3) run "/etc/continue hdisk#" - Check out the article on "running /etc/continue" 4) Check to see if /etc/filesystems has the /usr filesystem in it. 5) use the mount command to check to see if /usr is mounted. 6) # cd /usr/bin If the command fails, then /usr/bin needs to be restored. 7) # ls -l /usr/bin/odmget If there is no odmget, then check to see if other files are missing from /usr/bin. LED C31 1) Boot from bosboot diskette or tape and get to install/maint menu - Key in service position 2) choose option 5 3) run "/etc/continue hdisk#" - Check out the article on "running /etc/continue" 4) chcons -a login=enable /dev/hft/0 5) reboot in normal mode. 6) If you still have LED C31, then repeat step 1-3, and goto step 7. 7) Next, # mkdir /etc/objrepos/bak # cp /etc/objrepos/Cu* /etc/objrepos/bak # cp /etc/objrepos/boot/Cu* /etc/objrepos # savebase Article on /etc/continue: 1) lqueryvg -? : Provides you the valid options and syntax 2) lqueryvg -p hdisk? -At : Provides you LV names, numbers and LV STATES 3) getlvodm -P : To aquire the association of the hdisk_name with the hdisk PVID 4) lquerypv -p PVID -N hdisk# -At grep LVID : Lists in column format (from L to R) PVID STATUS LVID EXTENSION LP# ----------------------------------------------------------------------------- The above commands should be run PRIOR to executing /etc/continue from maintenance mode if you find that you are having problems getting filesystems to mount or are getting error messages executing /etc/continue that may be related. The reason for this is that the Installation/Maintenance Diskettes will assign an hdisk name to a PV that may/will be different from the names the customer is familiar with when booted in Multi User Mode. I will illistrate the command and its output providing information that will be needed to help determining many things prior to executing /etc/continue. The order in which the illistration is given should be the order in which the commands should be executed, Most of the time. NOTE: that if you are working with a 552 LED then this procedure will provide you with the hdisk name for the command 'bosboot -a -d hdisk?' START: 1) Your first step is to locate PV's that are part of the rootvg. To do this GOTO step 2. *) After issuing the command 'getlvodm -P' write down all the hdisk_names as sociated with the rootvg. This command will show the the VG's the hdisk(s) are ass ociated with only if importvg and varyonvg have already been run. (ie. after /etc /continue) Otherwise this command is good to see if the system recognizes any hard d rives. 2) Now you will need to find out which PV contains hd5 (blv) GOTO step 3 * ) After issuing the command 'lqueryvg -p hdisk? -At' look for hd5 and writ e down the LVID number (ie. 00000503b567e4.3). Its this number you will have to search for in the next step. 3) Now the goal is to find out which PV the hd5 LV resides on. Once you find th is you will know which Hdisk_name to supply the /etc/continue command GOTO step 4 * ) NOTE: You do not have use of the 'pg' command. Use Ctrl-s and Ctrl-q to scroll You will issue the 'lquerypv -p PVID -N hdisk_name -At' once for each hd isk associated with the rootvg until you spot the LVID for hd5 on the output . ----------------------------------------------------- First: # lqueryvg -? lqueryvg: illegal option -- ? Usage: lqueryvg -g VGid -p PVname -NsFncDaLPAvt ----------------------------------------------------- Second: # getlvodm -P +------------------------------------------- hdisk_name +----------------------- PVID +-------- VG_Name +--+--+ +-------+------+ +--+--+ hdisk0 00000305b28a03e1 rootvg hdisk1 00000305b23ff460 rootvg ----------------------------------------------------- Third: # lqueryvg -p hdisk0 -At Max LVs: 256 PP Size: 22 Free PPs: 43 LV count: 11 PV count: 2 Total VGDAs: 3 +----------------------- Logical Volume Identifier (LVID) +------------- Minor device number (see /dev) +-------- Logical Volume Name (LVN) +----- LV state C ( 0 indicates LV is not defined to a VG ) C ( 1 indicates LV is defines to a VG ) ( 2 indicates LV has stale logical partitions ) +------+-------+ Logical: 00000305b2403191.1 hd6 1 00000305b2403191.2 hd61 1 00000305b2403191.3 hd5 1 00000305b2403191.4 hd7 1 00000305b2403191.5 hd8 1 00000305b2403191.6 hd4 1 00000305b2403191.7 hd2 1 00000305b2403191.8 hd3 1 00000305b2403191.9 hd1 1 00000305b2403191.10 paging00 1 00000305b2403191.11 lv00 1 +-------------- Number of VGDA's +---------- State Physical: 00000305b28a03e1 2 0 00000305b23ff460 1 0 +---+--+ +--------------------------------------- Type of H.W. (See uname -m) ----------------------------------------------------- Fourth: /* Note this command is run once for each PVID the customer has */ /* Make sure you change the hdisk_name to match the PVID number */ /* See the "getlvodm -P" command for PVID's and hdisk_names */ /* See "lqueryvg -p hdiskX -At" for LVID's */ # lquerypv -p PVID -N hdisk_name -At grep LVID PP Size: 22 PV State: 0 Total PPs: 76 Alloc PPs: 38 Total VGDAs: 2 +---------------------------------- PVID +------------------------- Minor Device number of a LV +------------------BD (0 indicates PP is free) CD (1 indicates PP is allocate d) CD (2 indicates PP has stale d ata) D (4 indicates PP is being re synced) ( See lvm.h ; PP STATES ) +----------------------------- ---------- LVID.VGID +-------------------- ---------- Minor Device number of a LV +---------------- ---------- LV number +-- ---------- 1st Alt Volume ID's +--- Minor Device number of a LV 2nd Alt Volume ID's +-------+------+ +-------+------+ +-------+-- ----+ +-------+------+ PVMAP: 00000305b28a03e1:1 1 ODMtype 00000305b2403191.3 1 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:2 1 ODMtype 00000305b2403191.3 2 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:3 1 ODMtype 00000305b2403191.4 1 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:4 1 ODMtype 00000305b2403191.4 2 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:5 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:6 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:7 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:8 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:9 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:10 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:11 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 ====================================================================== >(U)9204. A Modem Setup Guide From: robinbatman.uucp (Robin D. Wilson) To set up modems in general requires an understanding of several important concepts: 1) (D)CD (Data) Carrier Detect. This is a voltage signal placed on pin 8 of the RS232 DB25 serial connector. It is used to tell the DTE (Data Terminal Equipment - in this case the computer to which the modem is attached) that the DCE (Data Circuit terminating Equipment - the modem) has established a logical 'wire' from point- to-point. In other words, we are connected from the serial port on your computer to the serial port on the other device to which you are attempting to communicate. 2) DTR (Data Terminal Ready). The DTE device is ready to talk. This is a voltage on pin 20 of the RS232 DB25 serial connector. It is intended to alert the DCE device to the 'existance' of the DTE device. (Sometimes this is used for a rudementary form of hardware flow control also... Turn off DTR == stop talking, Turn on DTR == start talking again.) Basically with a modem this is used to signal to the modem that the DTE (in our case the computer) is ready to talk. Usually this means that the tty has been opened (by either a "getty" process or some other program - like "cu") and the modem should enable "Auto-Answer" and prepare to accept commands. When DTR drops, the modem should interpret this as "the DTE device has been shutdown... time for me to hang up". 3) Flow control. This can either be accomplished through hardware or software. Hardware flow control can take many forms, but for modems there is really only one standard: RTS/CTS. This form of flow control uses a voltage on pins 4 and 5 (RTS and CTS pins) to signal to both sides of the connection when either side can accept data. If the voltage goes away, the other side should stop sending data. Software flow control usually takes the form of XON/XOFF flow control. This is a character that is placed into the stream of data going from one side to the other. When the other side receives the XOFF character, it should stop sending, when it receives an XON character it can start back up again. (There are more serious limitations to the software flow control methods because some programs generate binary data that could equal either an XON or an XOFF character. This means that the serial device will strip those bits out of the data assuming that they were intended for flow control, when in reality they were part of the data. The other limitation is: if the remote side has sent an XOFF to the local side (or visa versa) then the local side is not allowed to send any data back to the remote side... including XOFF or other flow control characters.) Enough with the basics. Now you want to know how to set up your IBM RS/6000 or your IBM RT to use a modem. There are two sides to the setup: the tty setup and the modem setup. The tty is fairly easy. For the most part your choice will be limited to the defaults from SMIT (for the RS/6000) or to the defaults from Devices (for the RT). There is; however, one area to which you will need to pay particular attention: do I intend for this modem to be used for dial-in, dial-out, or bi-directionally? One ofthe following settings for "Enable LOGIN" (on the RS/6000) or "Automatic Enable" (on the RT) will need to selected based on what you want to do: DISABLE: Use this setting if you only want to use the port for dial-out type connections. Basically, this setting does nothing but configure the serial port. No getty process is started, nobody can login on this port (unless you decide to "penable, or pshare, or pdelay" the port at some later point). ENABLE: This setting is best used for terminals (ie. not for modems), but it can work for "dial-in" only modem connections. This setting starts a "getty" process on the port. This getty started in this manner immediately locks the port, preventing any other process from using the port. Then, when getty sees the CD signal come up on the port, it sends a login herald, allowing the remote user to login. (IT IS SIGNIFICANT that the login herald is sent AFTER CD comes up. Think about it like this... "the modem brings up carrier AFTER it has negotiated the speed and connection parameters -- a "carrier frequency" -- with the remote modem, so getty doesn't send the login herald until the remote system/terminal is attached.") SHARE: This setting works well for "bi-directional" modem use. This setting causes a "getty -u" process to be started on the port. The "getty -u" is the classic AT&T "uugetty" process. Basically this type of getty starts on the port, and then waits for carrier to come up before attempting to lock the port. This allows other programs to open the port, create a lock, and prevent the getty from locking the port. As an example, the port is "share'd", but I want to use it to dial-out using the "cu" program. I issue the cu command, and cu opens the tty, and locks the port. I connect to the remote modem, CD comes up. (Remember that "getty" is still running, and just waiting for CD to come up.) Getty attempts to lock the port now (because CD came up), but "cu" has already locked the port so getty can't get a lock. The "getty" process then goes into a loop, "Do I have CD? Yes. Can I get the lock? No. Do I have CD? ..." When the "cu" process exits, CD is down, so the "Do I have CD?" part of the loop fails, and getty just loops on that function. When CD comes up due to someone dialing-in, and no other process has the lock, getty says: "Do I have CD? Yes. Can I get the lock? Yes. Great| issue a 'login:' herald." (Imbellishments added by the writer - you get the general idea.) DELAY: This setting is nearly identical to the "SHARE" setting, except the getty is called as: "getty -r" (which is the same as the AT&T uugetty -r) and this version of getty is waiting to see a character on the serial input buffer (read() on the tty doesn't return '0'). before it attempts to lock the port. So in the paragraph above, just replace all occurances of "CD" and "Carrier" with "Character on the serial input buffer". The modem setup can get a great deal more complicated. Since there are so many different brands of modems, each with their own setup parameters and commands, I will attempt to address them in a "generic" HAYES compatible manner, and let the reader find the equivalent settings for his particular brand modem. Try to remember that most modems have settings for all of these parameters, but some modems call them different things, and some divide them into "sub-categories" that are not discussed here. I will try to explain why the settings are necessary, so that confusion can be limited. You will need to make the following configurations for your modem: CD (Carrier, DCD, Data Carrier Detect, even CO) should be set to follow "true" carrier. This means that it is not "strapped high" on the modem, and that it only goes high when the remote modem is connected to the local modem. The reason this is important relates back to the 'getty' settings described above. If getty is waiting for carrier to lock the port and/or send out the login herald; strapping carrier high will defeat the purpose of having distinct settings for "ENABLE" and "SHARE" (ie. they will work functionally the same). Also, having getty echo a login herald to an unconnected modem can cause a loopback condition. The modem should usually be set to "echo" back the commands you type; but when you send the "login:" herald, it echos that back too. Getty will echo everything you type, so the login herald is echoed back to the modem, which echos it back, ad infinitum. If there is no carrier until a connection is made, then; when getty sends the "login:" herald, it is not echoed back, it is sent on to the remote terminal. Finally, if you strap carrier high on the modem, the serial port device driver will not know when the connection has gone down. For example, if the remote modem is powered off during a connection, the local modem will sense this, and hang up... BUT the local shell process on the computer will see carrier up (because the modem is set to "ALWAYS" present CD) and never log the user off. The next person who calls in, will be able to use the previous user's shell. This is (needless to say) a severe security risk. On the HAYES "V-Series" modems, the correct setting is: AT&C1. NOTE: If you use the "tip" program for dialing out, you NEED to strap carrier high on the modem. This is because "tip" is designed to work with carrier on the port only. (The port is opened, but IO to the port is blocked until carrier detect is high. This has to do with the way the port is opened using the "open()" system call.) To strap carrier "ALWAYS" high on a HAYES "V-Series" modem, enter the command: AT&C0. DTR should be set to "hang up" and "disable auto-answer" when the DTE device drops DTR. Most modems will come with the factory default set to ignore DTR signals from the DTE. This way, the modem will "auto-answer" right out of the box. This is not what you really want. On the RS/6000 the DTR signal is raised when the tty device is opened with the 'open()' system call. This means that "getty" will cause DTR to be to be raised and the modem will be able to "auto-answer" only when there is a getty running on the port. The other part of the equation is that the modem should hang up when DTR drops. On most SysV type machines, the "stty" setting of "hupcl" (Hang UP on last CLose) will cause DTR to drop on the last "close()" of the open tty file descriptor (in other words, when the last process using the port releases it, the device driver will stop asserting DTR). This is the way the computer signals to the modem to "hang up" the connection. On HAYES "V-Series" modems, there are 2 possible settings: AT&D2 (hang-up, disable auto-answer, and enter command state when DTR is not present); and AT&D3 (hang up, disable auto- answer, "RESET - reload operating parameters", and enter command mode when DTR is not present). The big difference is: "RESET". This means that if you made changes to the software switch settings, and then dropped DTR without saving the changes, they would be lost. On the other hand, if someone else made changes to the software switches, and you had the AT&D2 setting, those changes would remain "in-force" until you reset them. Most people prefer AT&D3. Auto-Answer should be enabled if you intend to allow other people to dial-in to your machine. On the HAYES "V-Series" modems this is software switch "S0=001". (Which sets the number of times to let the phone ring to "001".) You can set this with the command: ATS0= (where equals the number of times you want the modem to let the phone ring before it answers). Try to remember if you intend to set this to something more than "1 ring", that most modems have a default "timeout" value that is set around 30 seconds. If the modem calling you doesn't get a "carrier" tone within that timeout it will hang-up, so setting a very large number of rings could make your connection rate somewhat unreliable. Command Response should be set to respond to "LOCAL" commands only. This one is a little tricky to describe. Most modems try to alert the local DTE device that there is activity coming in from the outside world. Normally, when an incoming call is detected the modem sends the string "RING" to the local DTE device. This means that string will be echo'd back to the modem (because getty will turn on the "echo" on the tty device). When the modem sees any characters coming into it on the receive serial line (the one coming from the local machine), it immediately "HANGS UP" and enters command state. This means that this "RING" string will cause your modem to hang up before making a connection to the remote modem. Also, if your modem doesn't exhibit the strange behavior of "hanging up" right as the connection is getting started, then it will still have the problem of the first user to the "getty" process running on the port will have the name "RING". So the long answer is... set command response to only respond to local commands. On the HAYES "V-Series" modems the "Q" register handles this. I have found that a setting of: "ATQ2" works fine. Flow control should be set according to the desired programs that you will be using. For most instances, if you are going to be doing any kind of file transfers, you will need to make sure that you are NOT using "XON/XOFF" flow control (the same caveat applies to the serial port setup as well). UUCP and xmodem for example use a form of checksumming or CRC error control, and these "checksums" or "CRC" values are binary numbers -- meaning they can take the form of ANY ASCII character sequence -- including the ^S and/or ^Q used for XON/XOFF flow control. UUCP and xmodem will not usually work with XON/XOFF (if they do work, it just means that the files you happened to transfer didn't cause a "checksum" or "CRC" value that matched the XON or XOFF characters). What happens is this: one system (either modem or serial port) is receiving data, and responding with a CRC. The receiver gets a packet of information that CRC's to include the binary value of '^Q'. This CRC is sent to the remote system. The device that expects "XON/XOFF" flow control sees the '^Q' as a flow control character, and assumes that it was not intended to be in the data stream; so it strips it out of the incomming data. Then, the system that was sending the packet receives the CRC (minus the bits that made up the '^Q') and thinks that it has received an invalid CRC, so it resends the packet (which will still have the SAME CRC value). For most connections you will either need to use RTS/CTS flow control, or "NONE" for flow control. (On UUCP and Xmodem file transfers flow control is not required, the size of the packets that each program sends is small enough that you don't have to worry about overrunning the receive speed of the remote systems serial line). On the IBM RT product "RTS/CTS" flow is not supported, so you must use "NONE" for any type of file transfer software. On the RS/6000 the "RTS" line discipline can be set, but setting it is cumbersome (at least on the current release of AIX v.3.1), so it is usually easier to use "NONE" on this machine as well. Use the following list for the HAYES "V-series" modems to determine how to set up specific flow control methods: XON/XOFF AT&K4 RTS/CTS AT&K3 NONE AT&K0 (By the way, it doesn't hurt to set "RTS/CTS" flow control on the modem even if the computer is not using any flow control.) By and large, these settings should allow you setup reliable uni/bi-directional modem connections for the IBM RS/6000 and RT products. If they don't help, or if I have left something out, please mail me a note and I will add the info to the next revision of this guide. NOTE: The "SHARE" and "DELAY" settings for the tty setup on the RS/6000 don't work correctly until the 3003 update. Make sure that you have at least the 3003 update on the RS/6000 before attempting to use "bi-directional" modem lines, or you will have alot of headaches. ====================================================================== ====================================================================== >From the Jargon File 2.9.4: Iron Age: n. In the history of computing, 1961--1971 --- the formative era of commercial mainframe technology, when big iron dinosaurs ruled the earth. These began with the delivery of the first PDP-1, coincided with the dominance of ferrite core, and ended with the introduction of the first commercial microprocessor (the Intel 4004) in 1971. See also Stone Age; compare elder days. >92.02.10 Table of contents: (I)92041. Netview/6000 Democode (I)92042. MENTOR GRAPHICS ANNOUNCES SUPPORT FOR THE RISC SYSTEM/6000 (U)92043. IBM AIX 5080 EMULATOR/6000 RPQ available (I)92044. X11perf Numbers are available. (I)92045. LED Codes for the /6000 (U)92046. E-Mail access to AIX public domain software library (I)92047. NEW REVISION OF "RISC SYSTEM/6000 - A BUSINESS PERSPECTIVE" BOOK (U)92048. Detecting Uninitialized Local Variables (U)92049. Something about real life FDDI usage. (U)92050. PCSIM in AIX 3.2 Support for LIM 4.0 (U)92051. What is NVRAM? ====================================================================== >(I)92041. Netview/6000 Democode 1. Order the documentation: TOOLS SENDTO YKTVMV TOOLS AIXTOOLS GET NETVIEW PACKAGE 2. Order the code: TOOLS SENDTO RALVM14 TOOLS IBMUNIX GET IMAGE BINZ regards Harald Schneider ====================================================================== >(I)92042. MENTOR GRAPHICS ANNOUNCES SUPPORT FOR THE RISC SYSTEM/6000 February 5, 1992 On January 21, 1992, Mentor Graphics Corporation announced that it was supporting the RISC System/6000 family for its Electronic Design Automation (EDA) software products. Mentor Graphics is a leader in the EDA market with sales of $406,547,000 over the last 12 months. Mentor Graphics has also been approved as an IBM Industry Application Specialist (IAS). Mentor Graphics has applications to address IC, ASIC (Application-Specific Integrated Circuits), PCB (Printed Circuit Board), and System designs. Mentor Graphics incorporates its solutions into the Concurrent Design Environment*. This environment consists of design automation tools and the Falcon Framework* for Concurrent Design. The Concurrent Design Environment aids in the design and coordination of all aspects of electronic systems, from concept to manufacturing. This environment is not limited to Mentor Graphics' tools. Through its Open Door program, third party EDA vendor and customer developed applications can be integrated into the Falcon Framework, giving the designer maximum flexibility to create the desired design environment. The first applications to be available on the RISC System/6000 will be Explorer Lsim* and GDT Designer*. Explorer Lsim is a mixed-signal, multi-level simulator used in the design of ICs, ASICs, PCBs and Systems. Explorer Lsim is built on a simulation backplane which allows disparate simulators to be integrated into a single simulation environment. Because of today's technology requirements, one simulator cannot provide a complete solution to all problems. Instead, many specialized simulators are needed, each focused on solving a specific design problem. Once integrated into the backplane, all algorithms can operate simultaneously within Explorer Lsim. GDT Designer is a complete, integrated system for designing full custom ICs and ASICs. GDT Designer includes a hierarchical schematic editor, a layout editor for physical design, on-line design rule checking, tools for placement, routing, and module generation, and Explorer Lsim for design verification. Other Mentor Graphics applications will be available before the end of the year. For information on availability dates for other applications, contact your local Mentor Graphics office or send a note to IBM4EDA at DFWVM04 with your account situation. * Concurrent Design Environment, Falcon Framework, Explorer Lsim, and GDT Designer are trademarks of Mentor Graphics Corporation ====================================================================== >(U)92043. IBM AIX 5080 EMULATOR/6000 RPQ available Excerpts from the original announcement: IBM AIX 5080 EMULATOR/6000 RPQ #: P88635 DESCRIPTION: =========== IBM AIX 5080 Graphics System Emulator/6000 (5080 Emulator) The 5080 Emulator is a software product which runs under AIX Version 3.1 (R) with PTF 2008 on the RISC System/6000 (TM) and requires Graphics Library (GL) support. The High performance 8 and 24 bit 3D Color Graphics Adapter and POWER GTO have been tested and are supported with the 5080 Emulator. The 5080 Emulator will support 5080 programs running either on a host System/370 (TM) or host System/390 (TM) or a local 5080 program running on the same RISC System/6000 (TM). Screen management is via IBM AIXwindows (TM) on a 5081 or 6091 display monitor. CADAM is a trademark of CADAM Inc. CATIA is a trademark of Dassault Systemes. CAEDS is a trademark of Structural Dynamics Research Corporation. AIX, RISC System/6000, System/370, System/390, graPHIGS, and AIXwindows are trademarks or registered trademarks of International Business Machines Corporation. Highlights: * Runs System/370 based 5080 applications on a RISC System/6000. * Dials and LPFK can be either real or "soft" (in a window). * Four button cursor is emulated with either a mouse or tablet input device. * Can support multiple 5080 sessions using X-Windows. * Up to 16 graphics addresses are supported by the MSLA adapter. * Direct coax attachment via 5088 or 6098. * Built-in measurement and debug tools. * 3270 supported via 3270 emulator under HCON. The IBM AIX 5080 Graphics System Emulator/6000 runs on the following models of the IBM RISC System/6000 family of Workstations: * POWERstation or POWERserver 320,520,530,540,550,730 APPLICATION RESTRICTIONS: The following functions are limited: - Pattern fill - Line pattern capabilities - Programmable cursor limited to 32X32 - Wide line styles - 5086 like setup panels - Pixel Operations Details of these restrictions can be found in the IBM AIX 5080 Graphics System Emulator/6000, 5080 Emulator Users Guide. THE FOLLOWING FUNCTIONS ARE NOT SUPPORTED: - Polygon fill picking - Line on line and underpaint - Full range of cursor colors - 5080 sub-polygons HARDWARE CONNECTIONS NOT SUPPORTED: - Digitizer - RS-232C Ports CONFIGURATIONS Supported configurations for the 5080 Emulator: A - 5080 Host Based Applications (such as CADAM (TM) / CATIA (TM) / CAEDS (TM) / graPHIGS (TM) etc. 1- Host 370 applications.---5088/6098---RISC System/6000 w 5080 Emulator. 2- Host 370 applications.---5088/6098---5088-11R/6098-1R---RISC System/6000 w 5080 Emulator. B - 5080 Native Application 1- RISC System/6000 w 5080 application and 5080 Emulator. PERFORMANCE There are many factors that will affect end user performance. Under specific conditions, the 5080 Emulator testing has shown graphics systems performance approximately equal to that of a 5085-1, while running one 5080 Emulator session. Actual results may vary. ====================================================================== >(I)92044. X11perf Numbers are available. X11perf numbers of the gt? adapters IBM Internal Use Only| Get them with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET X11PERF2 LIST3820 or TOOLS SENDTO DALVM41B IBMPC AIXDOC GET X11PERF2 LIST3820 ====================================================================== >(I)92045. LED Codes for the /6000 AIXTOOLS: Information: RS-LEDS PACKAGE created by TUTEN at AUSVM6. text file of RS-6000 LED error codes Get them via TOOLCAT AIX ====================================================================== >(U)92046. E-Mail access to AIX public domain software library The following description is meant for IBM internal users, but anyone who can mail on ther Internet or Usenet can use this form of access. (afx) VM users who have INTERNET access can now use the INOTE facility to retrieve information from the AIX Public Domain Software Library System. Users desiring information from the library should send mail to: serveraixpdslib.seas.ucla.edu This AIX Competency Center service, provided by the UCLA School of Engineering and Applied Science, supports the following commands: Command Retrieves ------- ------------------------------------------------ help information on e-mail access to the library system list a current directory listing of software entries on the library system (/u/ftp/pub/ls-lR) send README library instructions at the root level send pub/README library instructions at the software directory level send pub/Deposit instructions on how to submit code which the user wishes to add to the Public Domain library send pub/Copyright GNU General Public License which contains the rules that submitters of code should ensure adherence to for meeting public domain tests The above commands MUST BE ENTERED as the "Subject:" of the e-mail note and are case sensitive. Please note the following examples: Correct Incorrect Subject: send README Subject: send readme Subject: send Readme Subject: SEND README The Subject: of notes sent to the userid will envoke actions according to the above list and send the results as an e-mail note to the requester. Only one command will be processed per message. This facility is also available to Internet users wishing to retrieve instructions via e-mail rather than the previously announced anonymous ftp access. This service was expedited at the expense of dial-in access because of the huge demand for IBM access to the library. Dial-in access is currently being tested and will be announced shortly. ====================================================================== >(I)92047. NEW REVISION OF "RISC SYSTEM/6000 - A BUSINESS PERSPECTIVE" BOOK February 7, 1992 IBM Mechanicsburg has just stocked the new 2nd Edition of "IBM RISC SYSTEM/6000 - A BUSINESS PERSPECTIVE" (GA23-2674) published by John Wiley & Sons. This highly successful book has been Updated to include the Model 320H, Model 950, Xstation 130, new graphics adapters including the 7235 POWER GTO, new extension to AIX, and more. This book contains complete information - all in one place - about the RISC System/6000 System Units, options, peripherals, operating systems, and application programs. Also included is a hands-on session with AIX's InfoTrainer for first time users. Finally, hypothetical small, medium, and large businesses are described and then outfitted with the appropriate RISC System/6000 hardware/software configurations to meet their needs. A companion to the highly successful "IBM PS/2 - A Business Perspective" (G325-0400) AND "IBM AS/400 - A BUSINESS PERSPECTIVE" (GA21-9990), this book describes the RISC System/6000 family in a way understandable by business people. Throughout the book, each feature of the RISC System is described in the context of how it helps the user do his job. IBMers, IBM Business Partners, and IBM Customers can also subscribe to receive future updates to these books through SLSS. CHAPTER 1: Introduces the RISC System/6000 family members. Then the technology (architecture, graphics, auxiliary storage, etc.) and functions are explained in non-technical terms. CHAPTER 2: Reviews the options (feature cards, upgrades, etc.) and peripherals (displays, printers, etc.) for the RISC System/6000 family. CHAPTER 3: GUIDES THE NEW USER THROUGH A 'HANDS-ON' SESSION WITH THE InfoTrainer education system. It then describes the basic types of SOFTWARE (APPLICATION PROGRAMS, OPERATING SYSTEMS, AND DEVICE DRIVERS) and how they work together. CHAPTER 4: Describes the basic types of application programs used with RISC System/6000 computers including cross-industry, industry specific, and custom alternatives with examples. CHAPTER 5: Discusses the AIX Operating system. First basic operating system concepts (i.e. batch vs interactive, multi-users, etc.) are defined in non-technical terms. Then AIX and its extensions are described. CHAPTER 6: Covers popular communications configurations in which RISC System/6000's can participate. These include remote terminals, Local Area Networks, and Wide Area (SNA and Non-SNA) Networks. CHAPTER 7: Discusses issues related to the selection of RISC System/6000 hardware and software to meet the needs of both commercial and technical users. Hypothetical organizations (small, medium, and large) are described and then outfitted with the right RISC System/6000 hardware and software to meet their needs. Then some other planning topics including identifying costs, identifying benefits, lease vs purchase, office ergonomics, and user training are discussed. Questions on this notice are to be forwarded to: HONE84(DEV3338) ====================================================================== >(U)92048. Detecting Uninitialized Local Variables It is undocumented, unsuported but still may be usefull. Might work only together with -O. Actually, there is an undocumented flag that may do what you want. It is -qdebug=undefuse. It puts a crude warning message in the listing file (English only) with a line number reference. Of course, you need to have a listing file so also specify -qsource or -qlist. It will not warn about automatics that may or may not be initialised - only those that it knows are not. The reason that this warning is not the default - or at least more official is because of bit fields. The way you initialise a bit field is to load up the word that contains it (garbage if this is the first reference to a word in automatic), twiddle the bits that you are interested in and store the whole thing back. It looks a great deal like the use of uninitialised automatic. I should probably put lots of disclaimers here like "use at your own risk" and "not officially supported" and "don't tell anyone you heard about it from me" so consider it done. ====================================================================== >(U)92049. Something about real life FDDI usage. Hi, do you still use good old Ethernet or Token Ring for your AIX environment, I'm up and running with FDDI-thanks to Lolo. Hardware / Hostnames 'fddi0':= 1*320, 20Mhz, 32 MB, 640 MB disk, 3D+, single attached FDDI,3007 'fddi1':= 1*320, 20Mhz, 16 MB, 560 MB disk, 3D+, single attached FDDI,3005 Network set up: (/etc/no -a) dog_ticks = 60 lowclust = 18 lowmbuf = 80 thewall = 2000 (pretty low| afx) subnetsarelocal = 1 maxttl = 255 ipfragttl = 60 ipsendredirects = 1 ipforwarding = 1 udp_ttl = 30 tcp_ttl = 30 arpt_killc = 20 tcp_sendspace = 16384 (pretty low| afx) tcp_recvspace = 16384 (pretty low| afx) loop_check_sum = 1 Test 1: fddiddt program (FDDI device driver test) Number I Total I MB/sec I Elapsed I CPU usage % Frames I of MBytes I I Time secI client I server =======+===========+========+=========+========+======= 10003 I 40.207 I 2.991 I 13.47 I 86 I 99 5003 I 20.104 I 2.953 I 6.81 I 84 I 99 1003 I 4.021 I 2.936 I 1.37 I 82 I 99 503 I 2.01 I 2.878 I 0.7 I 77 I 98 253 I 1.01 I 2.773 I 0.36 I 75 I 97 103 I 0.402 I 2.529 I 0.16 I 75 I 96 53 I 0.201 I 2.273 I 0.09 I 79 I 92 =======+===========+========+=========+========+======== Notes: * Server was fddi0 (32 MB RAM) * Client was fddi1 (16 MB RAM) * Reversed client/server did not changed the values * there was no other load on the systems (no X,NFS,etc.) Result: * the sender (client) is faster than the receiver (server) * memory has no influence in this test/configuration * the CPU's are the bottelneck's (**IMPORTANT**) * I will redo the test next week on two 550 machines (41 Mhz) Test 2: Spray test shell script (sending 300000 packets over the net) #|/bin/ksh /usr/etc/spray fddi0 -l 1 >> /tmp/stat & sleep 1 /usr/etc/spray fddi0 -l 1 >> /tmp/stat & sleep 1 /usr/etc/spray fddi0 -l 1 >> /tmp/stat & # end of file File: /tmp/stat sending 100000 packets of lnth 86 to fddi0 no packets dropped by fddi0 346 packets/sec, 29771 bytes/sec sending 100000 packets of lnth 86 to fddi0 no packets dropped by fddi0 345 packets/sec, 29739 bytes/sec sending 100000 packets of lnth 86 to fddi0 no packets dropped by fddi0 338 packets/sec, 29129 bytes/sec sar output: AIX fddi0 1 3 000028493100 02/07/92 ======================================== 15:59:48 %usr %sys %wio %idle Average 12 86 0 2 AIX fddi1 1 3 000023083100 02/07/92 ======================================== 15:59:18 %usr %sys %wio %idle Average 11 89 0 0 Result: * no packet was dropped (fddi driver quality, good job Austin) * again the CPU's are the bottelneck's Test 3: ftp (put/get) of a big file to create a 'big' file, I tar'ed the '/unix' file using the file /tmp/list File: /tmp/list: /unix /unix /unix /unix /unix /unix ==>> tar -cvf/tmp/big -L /tmp/list ls -la /tmp/big shows: -rw-r--r-- 1 root system 7700480 Feb 07 16:12 big 7700480 sent in 6.266 seconds (binary mode) 1202 Kbytes/s 7700480 received in 6.413 seconds (binary mode) 1173 Kbytes/s Notes: * now we have real disk I/O * fddi1 has a non SCSI 160 MB disk * more processor power would speed up a lot Test 4: rcp test of the big file on fddi0 # time rcp fddi1:/tmp/big /tmp/big > real 0m18.75s > user 0m0.91s > sys 0m10.91s hope this helps - frank :-) ====================================================================== >(U)92050. PCSIM in AIX 3.2 Support for LIM 4.0 To use Expanded Memory do the following: 1) Copy the driver shipped with the simulator /usr/lpp/pcsim/samples/PCSIMLIM.SYS into your DOS filesystem, for example: 'doswrite -D/dos3.3 /usr/lpp/pcsim/samples/PCSIMLIM.SYS PCSIMLIM.SYS' or 'cp /usr/lpp/pcsim/samples/PCSIMLIM.SYS /dos3.3' depending on whether /dos3.3 is a file or directory. 2) Invoke the Simulator with 'pcsim -xmem 4096 -save' to request 4Mb of extended memory (or however much you need) and save it in your profile (simprof). The parameter 4096 is the size of extended memory in 1Kb units. 3) Add to your \CONFIG.SYS file the following line: device=c:\pcsimlim.sys FRAME=D000 /X:256 The parameter 256 is the number of "frames" each of 16Kb. 4) Reboot (Ctrl-Alt-Del) or restart the Simulator. Arturo Martin-de-Nicolas ====================================================================== >(U)92051. What is NVRAM? Sometimes people ask what is meant by NVRAM or by clearing the NVRAM. NVRAM stands for Non Volatile Random Access Memory. So this memory is not lost because there is a lithium battery that powers it when the machine is turned off. It stores some configuration info, for example from which device to boot and other essential information. Clearing the NVRAM amounts to - shutdown the machine - power it off - disconnect the lithium battery - short circuit the memory, NOT the battery| (a paper clip might be handy for this. This step is needed to clear a capacitor that would help the memory to survive a battery change. - connect the battery again and boot in service mode with the maintenance disk. Now your NVRAM is updated to know about the adapters and it thinks hdisk0 (the first on the first SCSI adapter) is the standard boot disk. This step is usually only needed a machine is severely confused. ====================================================================== ====================================================================== System administrator error: core dumped.... :-) (or the NLS version: 4125-001: A system administration error has occurred. The offending system administrator has been sacked. Please contact your IBM service representative to obtain a new system administrator. :-) >92.02.14 Table of contents: (I)92052. GPC news (I)92053. NQS available internally (U)92054. X/Open Publications (I)92055. SUPPORT for 7202 EXPANSION RACK ON 550 & 560 via RPQ (U)92056. su log on AIX 3.1.5 (U)92057. how to build X contrib clients (I)92058. 1 GB drives input (U)92059. CHANGING THE LOCAL TSAP OF OSIMF FTAM (U)92060. Gradient Technologies PC-DCE (DCE for PCs|) (U)92061. New O'Reilly book on PHIGS (actually PEX SI) ====================================================================== >(I)92052. GPC news Since the class we organized on the GPC last year, there are some changes. This list summarizes those: 1- Instead of the LITERAL:LIBERAL GPCmark, we use the terms LITERAL:OPTIMIZED LITERAL: for those who want to get the performance by minimizing the opti- mizations OPTIMIZED: for those who want to get the maximum performance of the platform 2- The GL port of the PLB program has been done by SGI and IBM: in the 4th quarterly report SGI provided the GPCmarks for the IRIS 4D/310VGX 5 and 10 SPAN IBM provided GL figures for the GTO, GT4X and sabine and it makes the GTO the fastest graphics adapter with the rs/6000 550 model for the pc_board ( which is the optimized figure ). Notice also the improvement of the GL port vs the grapHIGS: head GTO,320H gP: 28.4:NA GTO,320H GL: NP : 40.6 3- Texas instrument has joined the GPC Committee 4- As you all know, you can get the latest GPCmarks in the HONE COMP database. 5- As you know also, our center distributes a demo tape. We have sent it to all the AIX porting centers and all who asked for. In this tape we have included the plb program and the 5 test-files. if you haven't got this tape , send a note to AIXTMSC at MUNIVM4 and ask for it 6- The last point: last week in La Hulpe , Al Bunshaft, Program manager of Advanced Graphics Hardware Development made a presentation about the AIX graphics strategy. He pointed out the GPC as THE graphics benchmark every- body should use to characterize a graphics workstation. To go in this direction, it would be good for IBM to propose new standard files characterizing a wider range of applications. And that is our job. So I am very keen to receive any suggestion and idea , for example an ISV willing to get his application as a standard file used by the GPC committee. For that,we have to work to the translation of his data into the BIF. I am waiting for your feed-back Mit freundlichem Gruss / Best regards Laurent ====================================================================== >(I)92053. NQS available internally There is now a package on AIXTOOLS that contains the NQS queueing system. AIXTOOLS: Information: COSNQS2 PACKAGE created by JBEHM at KGNVMA. COSMIC NQS V2.0 - UNIX batch queueing system And there is also a forum on IBMUNIX to discuss it: IBMUNIX: Information: NQSBATCH FORUM created (and is publicly appendable) by JBEHM at KGNVMA. To discuss NQS batch queueing software ====================================================================== >(U)92054. X/Open Publications Here is the list of X/Open publications for February. It contains all those publications in print and due to be printed in the near future. Regards Cathy ---------------------------------------------------------------------------- Cathy Hughes X/Open Company Limited Apex Plaza, Forbury Road, Email: cy.hughesxopen.co.uk Reading, Berkshire, Tel: +44 734 508311 ext 2261 RG1 1AX, England Fax: +44 734 500110 Tel: +44 734 508311 ---------------------------------------------------------------------------- X/Open Publications ------------------- For all orders and ordering information, please contact: X/Open Company Limited (Publications) PHM Oakwood House St. John's Estate Penn, High Wycombe Bucks, HP10 8HQ Tel: 0494 813844 Fax: 0494 816849 X/Open Ref Price ---------- ----- General ------- Open Comments Subscription $ 0.00/UKL 0.00 Branded Systems List BRO/LIST/90/010 $ 0.00/UKL 0.00 XPG4 Snapshots - Three Volume Set T001 $150.00/UKL 95.00 Open Systems Directive O201 $500.00/UKL300.00 Was Open Systems Directive (Xtra '90), XO/OSD/91/001 1/91" Data Interchange ---------------- CD-ROM Support Component (XCDR) XO/PRELIM/91/020 $ 49.00/UKL 30.00 X Window System File Formats and Appln Conventions XO/CAE/91/070 $ 49.00/UKL 30.00 API to Electronic Mail (X.400) XO/CAE/91/100 $ 65.00/UKL 40.00 Was API to Electronic Mail (X.400), XO/PRELIM/91/010 4/91" Byte Stream File Transfer (BSFT) XO/CAE/91/400 $ 65.00/UKL 40.00 Was BSFT (Byte Stream File Transfer), XO/PRELIM/90/010 6/90" EDI Messaging Package (XEDI) XO/PRELIM/91/050 $ 57.00/UKL 35.00 Message Store API XO/PRELIM/91/060 $ 65.00/UKL 40.00 Data Management --------------- Data Management XO/XPG/89/006 $ 30.00/UKL 22.95 Indexed Sequential Access Method (ISAM) XO/DEV/90/010 $ 49.00/UKL 30.00 SQL Remote Database Access XO/SNAP/91/030 $ 40.00/UKL 25.00 Structured Query Language (SQL) XO/PRELIM/91/030 $ 49.00/UKL 30.00 Was Structured Query Language (SQL), XO/SNAP/91/020 1/91" Internationalisation -------------------- XSI System Interface and Headers XO/XPG/89/003 $ 30.00/UKL 22.95 XSI Supplementary Definitions XO/XPG/89/004 $ 30.00/UKL 22.95 Protocols for X/Open PC Interworking: (PC)NFS XO/DEV/90/030 $ 49.00/UKL 30.00 Protocols for X/Open PC Interworking: SMB XO/DEV/91/010 $ 57.00/UKL 35.00 Guide to IPS-OSI Coexistence & Mig'tion XO/GUIDE/91/040 $ 49.00/UKL 30.00 System Interfaces and Headers XO/SNAP/91/060 $ 85.00/UKL 50.00 COBOL Language XO/CAE/91/200 $ 65.00/UKL 40.00 EDI Messaging Package (XEDI) XO/PRELIM/91/050 $ 57.00/UKL 35.00 X/Open Transport Interface (XTI) XO/CAE/91/600 $ 65.00/UKL 40.00 Was Revised XTI (X/Open Transport Interface), XO/DEV/90/060 12/90" Message Store API XO/PRELIM/91/060 $ 65.00/UKL 40.00 Internationalisation Guide XO/GUIDE/91/030 $ 65.00/UKL 40.00 Interworking ------------ Networking Services XO/XPG/89/008 $ 30.00/UKL 22.95 Comparison Study of OSI Profiles XO/SNAP/90/010 $ 49.00/UKL 30.00 Interworking API Style Guide XO/SNAP/90/030 $ 49.00/UKL 30.00 Guide to the Internet Protocol Suite XO/GUIDE/91/010 $ 49.00/UKL 30.00 Protocols for X/Open Interworking: XNFS XO/CAE/91/030 $ 52.00/UKL 32.00 API to Directory Services (XDS) XO/CAE/91/090 $ 65.00/UKL 40.00 Was API to Directory Services, XO/PRELIM/90/030 12/90" Guide to Selected X.400 and Directory Services APIs XO/GUIDE/91/050 $ 49.00/UKL 30.00 OSI-Abstract-Data Manipulation API (XOM) XO/CAE/91/080 $ 65.00/UKL 40.00 Was API to OSI Object Management (XOM), XO/PRELIM/90/040 1/90" X/Open Transport Interface (XTI) XO/CAE/91/600 $ 65.00/UKL 40.00 Was Revised XTI (X/Open Transport Interface), XO/DEV/90/060 12/90" Mainframe Data Access --------------------- CPI-C XO/DEV/90/050 $ 49.00/UKL 30.00 SQL Remote Database Access XO/SNAP/91/030 $ 40.00/UKL 25.00 Operating System Services ------------------------- XSI Commands and Utilities XO/XPG/89/002 $ 30.00/UKL 22.95 XSI System Interface and Headers XO/XPG/89/003 $ 30.00/UKL 22.95 XSI Supplementary Definitions XO/XPG/89/004 $ 30.00/UKL 22.95 System Interfaces and Headers XO/SNAP/91/060 $ 85.00/UKL 50.00 Commands and Utilities XO/SNAP/91/070 $ 85.00/UKL 50.00 Basic Definitions XO/SNAP/91/080 $ 45.00/UKL 30.00 Programming Languages --------------------- Programming Languages XO/XPG/89/005 $ 30.00/UKL 22.95 COBOL Language XO/CAE/91/200 $ 65.00/UKL 40.00 Security -------- Security Interface Specs: Auditing and Authentication XO/SNAP/90/020 $ 49.00/UKL 30.00 Security Guide (Second Edition) XO/GUIDE/90/010 $ 49.00/UKL 30.00 System Management ----------------- Systems Management: Problem Statement XO/SNAP/91/010 $ 25.00/UKL 15.00 Systems Management: Reference Model XO/SNAP/91/040 $ 25.00/UKL 15.00 Management Protocol Profiles (XMPP) XO/PRELIM/91/080 $ 25.00/UKL 15.00 Transaction Processing ---------------------- Distributed TP: Reference Model XO/GUIDE/91/020 $ 25.00/UKL 15.00 Distributed TP: The XA Specification XO/CAE/91/300 $ 49.00/UKL 30.00 Was DTP: The XA Specification, XO/SNAP/91/050 6/91" User Interface -------------- Window Management XO/XPG/89/007 $ 30.00/UKL 22.95 X Window System Protocol XO/CAE/91/050 $ 49.00/UKL 30.00 X Toolkit Intrinsics XO/CAE/91/060 $ 49.00/UKL 30.00 X Window System File Formats and Appln Conventions XO/CAE/91/070 $ 49.00/UKL 30.00 Xlib - C Language Binding XO/CAE/91/040 $ 65.00/UKL 40.00 Work Station Data Access ------------------------ Protocols for X/Open PC Interworking: (PC)NFS XO/DEV/90/030 $ 49.00/UKL 30.00 Protocols for X/Open PC Interworking: SMB XO/DEV/91/010 $ 57.00/UKL 35.00 Protocols for X/Open Interworking: XNFS XO/CAE/91/030 $ 52.00/UKL 32.00 IPC Mechanisms for SMB XO/CAE/91/500 $ 65.00/UKL 40.00 Was IPC Mechanisms for SMB, XO/PRELIM/91/040 8/91" ====================================================================== >(I)92055. SUPPORT for 7202 EXPANSION RACK ON 550 & 560 via RPQ Note that this is an RPQ| February 11, 1992 The POWERstation/POWERserver 550 and 560 now support the attachment of one IBM 7202 Expansion Rack, with up to two 6210 High-Performance Disk Drive Subsystem Adapters and up to six IBM 9333 Model 010 Drawer High-Performance Disk Drive Subsystem Drawers. This support is related to the RPQ 8A0601, which provides support for the installation of up to two 6210 High-Performance Disk Drive Subsystem Adapters and allows attachment of up to six High-Performance Disk Drive Subsystem Drawers to the POWERstation/POWERserver 550 and 560. Questions on this notice are to be forwarded to: AUSVMQ(ANNE). ====================================================================== >(U)92056. su log on AIX 3.1.5 3.1.5 doesn't provide the sulog capability. You can use the AIX auditing subsystem to provide the same function. The sulog is there in 3.2. To obtain the /usr/adm/sulog functionality of Unix, you must customize and enable the AIX auditing subsystem. This is not a difficult task, however there are several steps. Also, keep in mind that that auditing is very flexible and powerful and what I will describe below is just a sample of what you can do with it. Note the following characters incase of translation problems: | is a "pipe" symbol & is an ampersand " is a double quote > is greater-than To configure sulog capability: 1) Decide where you want the sulog file to live. It has been suggested that /usr/adm/sulog is a good place. 2) login as root 3) cd /etc/security/audit 4) vi streamcmds Delete the existing line at the top of the file, and add the following line: (note this is all one line, and will wrap. Do not split into multiple lines) (also, insert your favorite path for the file where this example specifies /usr/adm/sulog) /etc/auditstream /etc/auditselect -e "event == USER_SU" /etc/auditpr -v > /usr/adm/sulog & 5) Save and exit the streamcmds file 6) vi config At the top of the config file, change the first stanza to read: start: binmode = off streammode = on 7) Save and exit the config file 8) To test the sulog capability, type (as root) audit start 9) Check for the existance of the /usr/adm/sulog file 10) Do a few su's (both successful and unsuccessful) and check the /usr/adm/sulog file for correct reporting. 11) To enable this capability automatically, edit /etc/rc and put the following line near the end /etc/audit start 12) If you would ever desire to pause the auditing, you can type audit off then type audit on to resume. 13) Note that whenever you type audit start, it seems to recreate the output file, so you may wish to change the line in the streamcmds file to append to the file ">>" or take other measures to save the old file. 14) Last of all, see the AIX Commands Reference Vol.1 under audit for more information. There is a "bin" mode of auditing that can compile an ongoing audit trail if you would like to do that. Good luck| Matthew J. Cleland IBM St Louis ====================================================================== >(U)92057. how to build X contrib clients If you are building X Windows from the MIT distribution tapes, you may find that the standard MIT distribution compiles fine (I did), but that contributed clients refuse to compile (I did). I got multiple errors complaining about strchr() not having the correct number of parameters. These programs would compile, however, under the distribution X11R4 directories (/usr/lpp/X11/Xamples/clients, etc). It appears that the Secret is to put the following into your ibm.cf: -D__STR31__ Note the DOUBLE UNDERSCORES before and after the Magic Word. From: Vance R. Bass AIX Systems Specialist, IBM Knoxville ====================================================================== >(I)92058. 1 GB drives input Would everyone that's interested in the 1 GB 3.5" drive that was announced last year, please send me a note. In the note, give me the quantity of aftermarket (MAXTOR, Seagate, Sony, Fujitsu, etc.) drives which would be displaced if the drives were available at a cost of $ 3,000.00 per drive and if they were available at $ 5,000.00 per drive. (I expect that the more expensive they are the fewer that would be sold.) Also if you could give me the quantity of OEM drives (non IBM) which you bid last year (1991). Quantity ------------------------------- $ 3,000.00 xxx $ 5,000.00 nnn Art Cannon ACANNON at DALVMIC3 ====================================================================== >(U)92059. CHANGING THE LOCAL TSAP OF OSIMF FTAM The local TSAP of OSIMF FTAM is predefined as x'0103'. The OSIMF manual is not clearly enough to show the way to change this value. For interoparational by a customer situation we found the way that another TSAP will work. Following files (shipped version is the base) must be changed. We use the new TSAP-ID 'A800FTAM'. /etc/osi.cfg: in section ns the first node_name block 'Mysap' change two lines to: TSAP_ID_Len 8 TSAP_ID 0x413830304654414d /etc/isoservices change the asap/filestore selection to: "asap/filestore" "A800FTAM" /etc/ftamd /etc/isoentities change the templates for services to default filestore 1.3.9999.1.7 "A800FTAM"/ ( is a backslash) and for make a test with yourself add a hostname like: a800 filestore 1.3.9999.1.7 ""/""/"A800FTAM"/NS+...your_ns_value... after restart the osistack and ftam by rc.osimf -ftam a connection for FTAM with 'open a800' works fine. - mc - thanks to J. Lockau ====================================================================== >(U)92060. Gradient Technologies PC-DCE (DCE for PCs|) Quoting Gradient Technologies letter dated Nov 27, 91: "Our current schedule is to ship Release 1.0 in April 1992 timeframe including Threads, RPC, Naming and Security. Later in 1992 we will be releasing an Extension Set including Distributed File Support, Time Service and a Remote Print Service." For further information contact: Gradient Technologies, Inc. 577 Main Street Suite 4 Hudson, Ma 01749 Tel.: 508-562-2882 Fax: 508-562-3549 Juergen Boettcher ====================================================================== >(U)92061. New O'Reilly book on PHIGS (actually PEX SI) There is a new book in the O'Reilly X series due to be available in February. I've seen a preview copy and it looks very good... PHIGS Programming Manual Tom Gaskins O'Reilly $39.95 Cheers Iain ====================================================================== ====================================================================== Warning: Too much brain may damage your life| >92.03.02 Table of contents: (I)92062. IBM RISC System/6000 Performance Brief (I)92063. IBM RISC SYSTEM/6000 Transaction Managers - Tuxedo TPC-A (U)92064. SNA Services/6000 Profile conversion (I)92065. AIXPress softcopy (U)92066. How to set up AIXwindows Interface Composer (I)92067. AIX PS/2 Support for Internal customers (I)92068. FTN softcopy on UUCP (U)92069. TRANSARC has anounced DCE for the RS/6000... (U)92070. 3.1 server for 3.2 install (U)92071. ISPF/PDF Dialog on the AIX (I)92072. Some CATIA tips for 3.2 (U)92073. GCC 2.0 formally released| (I)92074. GCC 2.0 formally released| - the internal version (I)92075. Installation of an IBM OEM 1 GB disk (U)92076. loading kernel extensions and getting nasty returns. (I)92077. FDDI performance (I)92078. /6000 configurator for the PC in Germany (U)92079. O'Reilly & Associates (Nutshell Books) Catalogue (U)92080. SCSI MICROCODE INSTALLP DISKETTE (long post) (I)92081. Internet Technology Handbook (I)92082. NCS - configuration/info ====================================================================== >(I)92062. IBM RISC System/6000 Performance Brief This unclassified performance brief comparing the performance of the RISC System/6000 systems to competitive systems has been updated and is now available on the PEC Tools disk. This brief may be given to customers. It contains performance data based on the following benchmarks : . SPEC Suite 1 (CPU intensive integer and floating point) . SPEC CINT92 (New CPU intensive integer suite) . SPEC CFP92 (New CPU intensive floating-point suite) . Linpack (100x100 Double precision floating point) . AIM (multi-tasking, C programs, UNIX utilties) . SPEC SDM 1 (multi-tasking, software development) . TPC-B (multi-tasking, database performance) . TPC-A (multi-user, online transaction processing) To obtain this package, please issue the following command: TOOLS SENDTO DALVM41B TOOLS PEC GET RS6KPB PACKAGE The TERS3820 files (3) in the package are large and will take time to get to you over the network. Use the README file for instructions on receiving, unpacking and printing. To subscribe to this package in order to receive updates automatically, please issue the following command: TOOLS SENDTO DALVM41B TOOLS PEC SUB RS6KPB PACKAGE If you have any questions or feedback, please send a note to PEC at DALVM41B. ====================================================================== >(I)92063. IBM RISC SYSTEM/6000 Transaction Managers - Tuxedo TPC-A A brief paper describing the way Tuxedo Transaction Manager works on the RS/6000 is available on the PEC Tools disk. Tuxedo is a Transaction Manager (also called Transaction Monitor or TM) developed by AT&T Laboratories. It is marketed by several vendors, usually under a different name. This software is available on the RS/6000 under the name OPEN/TP1 and it is distributed by Ally Software, a subsidiary of UNISYS. The paper describes the use of Tuxedo and the TPC-A implementation using Tuxedo in a RS/6000 client/server configuration. It describes basic application programming, Tuxedo configuration, and maintenance functions. To obtain a copy of this report, please issue the following commands; TOOLS SENDTO DALVM41B TOOLS PEC GET DOCTUXG PACKAGE TOOLS SENDTO DALVM41B TOOLS PEC SUB DOCTUXG PACKAGE The first command will get the package to you and the second will ensure that you receive updates automatically. Read the README file that comes with the package to get information on how to print the LIST3820 file. A complete list of all the PEC performance information can be found in the "PEC PERFORMANCE INDEX" article in the HONE/COMP database. Please send any questions or comments to PEC at DALVM41B, or just fill in the FBFORM that comes with the package and return to the author. ====================================================================== >(U)92064. SNA Services/6000 Profile conversion IMPORTANT| AIX VERSION 3.2 SNA SERVICES/6000 PROFILE CONVERSION Updating to AIX Version 3.2 requires SNA Services/6000 profile conversion from AIX Version 3.1 format. SNA Services/6000 provides an awk script which will convert profiles exported from an AIX 3.1 system to the required AIX 3.2 format. HOWEVER, this awk script changes the first 3 digits of the XID Node ID (known as the IDBLK) in all Control Point Profiles to 071. Although the default IDBLK for the RISC System/6000 is 071, other values are acceptable. There is a replacement awk script which will not modify the XID Node ID in the Control Point profiles. Please order this script with the following command (enter from the PROFS command line): TOOLS SENDTO DALVM41B TOOLS AIXIC GET AIX32AWK PACKAGE Also, the following HONE item gives detailed steps for using the AIX 3.2 awk conversion scripts. HOWTO AIX: CONVERTING SNA SERVICES/6000 CONFIGURATION PROFILES TO AIX VERSION 3.2 FORMAT (ITEM: 1VPCB) ====================================================================== >(I)92065. AIXPress softcopy "AIXPRESS" PERFORMANCE NEWSLETTER NOW AVAILABLE AS LIST3820 FILE The "AIXPRESS" performance newsletter is an informal, more or less quarterly publication of the Austin Personal Systems Programming Center, AIX System Performance Group. The newsletter regularly publishes articles about performance related topics. Most articles have been directed toward the RISC System/6000 and AIX , but there have been some articles about competitors' systems. The intended audience is the community of AIX SE's. Even though the scope of the articles generally extends beyond the novice, there is a wealth of information presented that will benefit all who read them. The current issue contains the following articles: AIX 3.2 Memory Load Control New VMM Page-Replacement Algorithm New Optimisations in the XL C and FORTRAN Compilers I/O Pacing Disk Throughput Performance FORTRAN Preprocessors Sometimes Improve Performance The Performance-Conscious Programmer Performance Tools and "AIXPRESS" Distribution Update The current issue (01/92) can be retrieved from the tools disk by issuing the following command from your VM account: TOOLS SENDTO DALVM41B TOOLS AIXIC GET PERF0192 PACKAGE A compilation of the most significant articles from previous issues will soon be available as PERF9091 . When it is available, it can be retrieved by issuing the following tools request: TOOLS SENDTO DALVM41B TOOLS AIXIC GET PERF9091 PACKAGE If you retrieve the January issue (PERF0192) or the AIXPRESS digest (PERF9091), your VM ID will automatically be added to the list of subscribers, which will ensure that you are notified when the next issue of AIXPRESS is available. Although most of the articles published in AIXPRESS have been written by members of the AIX System Performance group, they welcome articles as well as comments and suggestions from other groups. Their VNET address is AIXPRESS AT AUSVM6 . ====================================================================== >(U)92066. How to set up AIXwindows Interface Composer Item 0VPCF Document ID Q577176 TITLE: 920214 HOWTO AIX: CONFIGURING AIXWINDOWS INTERFACE COMPOSER (AIC) FOR PROPER EXECUTION SCENARIO/EXPLANATION: THIS HOWTO DETAILS HOW TO SET UP AIC SO THAT aic will execute. If AIC has not been configured correctly, the user may receive the error message: "5756-141 Could not connect to AIC license server at " when the aic command is entered. SOLUTION: AIC comes with its own license server. There is an intermittent problem with AIC license daemon not starting properly. To correct the problem perform the following steps as the root userid: 1. Enter the command: hostname Write down the hostname for later use. 2. Enter the command: uname -m Write down the results (serial number) from the command for later use. 3. Enter the command: cd /usr/lpp/aic/bin 4. Enter the command: aickeygen 1600 where is from step 1 where is from step 2 where is the number of licenses purchased for the machine. In most cases this number will be 2. 5. Enter the command: stopsrc -s aicd This will stop the aic license server and kill any executing aic programs. 6. Enter the command: startsrc -s aicd This will start the aic license server. 7. Enter the command: aic Aic will be started. NOTE: If AIC does not start or you still get the same message then it will be necessary to re-boot the machine. Once the machine has been re-booted aic will start without any problems. ====================================================================== >(I)92067. AIX PS/2 Support for Internal customers Document ID G010282 TITLE: DSSC FLASH 2049 CHANGE OF SERVICE FOR IBM INTERNAL CUSTOMERS ON AIX PS/2 1.2.1 Effective 3/1/92, service for IBM internal customers on AIX PS/2 1.2.1 will be limited to high-impact problems reported on production systems only. Existing problem management (PMR) and defect (APAR) records will be reviewed against the following definition. Those not meeting it will, with customer concurrence, be closed. IBM representatives, who report problems for customers, are requested to use the account number of their customer rather than their IBM internal number. Definition: High-impact problems on production systems are defined as those problems that prevent customers from accomplishing the business purposes for which AIX PS/2 was obtained. It is further defined as being problems of significant financial impact to IBM's business. Problems typically reported as Severity 2, 3 and 4, or those that can be worked around should not be reported. Examples of high-impact problems on production systems are: boot failures, panics, data corruption, ... etc. After 2/29/92, IBM internal customers will no longer report problems via phone. The IBM Support Center will continue to accept problems reported by IBM internal accounts, but the method of communicating them will be electronic. Customers with access to the Austin token ring can use the script AIXBUGS; others will use the VM Network. AIXBUGS can be obtained by sending EMAIL to aixbugs@ease.austin.ibm.com. To use VM for problem reporting, customers will need to obtain a copy of the VM EXEC called "AIXRPT," by sending a PROFs note to LIBPS2 @ AUSVMQ. Electronic problem reports will be screened by the Support Center on a daily basis and acted on as appropriate. Those of obvious high impact will be responded to immediately; others will be investigated as time permits. The IBM Support Center will contact customers for additional information on reported problems of questionable impact. Those not able to meet the criteria will, with customer concurrence, be cancelled. Problems can be avoided by keeping systems at the current service (PTF) level. PTF service will continue to be available to IBM internal customers as soon as released and it is suggested that they be installed as soon as possible to avoid previously discovered problems. They can be obtained by contacting the IBM Support Center via electronic access as described above. Escalations associated with this change should be directed to PSLOB management, as shown below. Those related to problems that will not be fixed in this release should first be directed to management at the Austin IBM Support Center, (see below) and then, if necessary, to PSLOB. IBM Support Center Phone T/L ID / NODE Anna-Marie Phelps (512)823-8860 793-8860 AMPHELPS @ AUSVM8 Leonard Piotrowski (512)823-8950 793-8950 LEONARD @ AUSVM8 Nick Comsudi (512)823-9200 793-9200 COMSUDI @ AUSVM8 PSLOB Management Karen Welch (407)982-8025 982-8025 WELCH @ BCRVMPC1 Louise Terry (407)443-2219 443-2219 LTERRY @ BCRVMPC1 Questions regarding these changes should be directed to Jerry Smok at (310) 337-5153 or SMOK @ BCRVMPC1 or BOCASMOK @ AUSVMQ. ====================================================================== >(I)92068. FTN softcopy on UUCP This presentation will give an overview of UNIX-to-UNIX CoPy (uucp), Call-to-UNIX (cu) and Call-to-Terminal (ct) as it relates to the AIX Operating System. This form of communication allows for file transfers and remote execution of commands on other systems. Information to be covered include what files and directories to use, systems and device configurations, command line examples and debugging hints and tips. TOOLS SENDTO DALVM41B TOOLS AIXIC GET FTN92044 PACKAGE Any inquiries concerning this broadcast or the handouts may be directed to the sponsor, Karen Rodriguez at DALVM41B(RODRIGUE). ====================================================================== >(U)92069. TRANSARC has anounced DCE for the RS/6000... From: fritz@scipp.UCSC.EDU (Frederick Staats) Transarc to Offer DCE Developers Kit Available for Sun SPARCstation and IBM RISC System/6000 Workstations PITTSBURGH, January 14, 1992---Transarc Corporation today announced a DCE Developers Kit running on Sun and IBM workstations, with first customer shipments to begin in March, 1992. The DCE Developers Kit is targeted at all application developers who want to begin porting existing applications --- or developing new applications --- based on the Open Software Foundation's (OSF) Distributed Computing Environment (DCE). The DCE Developers Kit, based on DCE Release 1.0 from the OSF, will be available initially for Sun SPARCstations running SunOS 4.1.2 (Solaris 1.0) and for IBM RISC System/6000s running AIX 3.2. "This is a very important step toward a comprehensive DCE strategy for end-users," commented Derek Brink, marketing executive for Transarc. "DCE must support the applications end-users need, and it must also be available on the dominant platforms in the installed base. Transarc's DCE Developers Kit is intended to help satisfy both of these requirements." For Sun customers, the DCE Developers Kit is the first tangible indication that they will be able to leverage their existing workstation investments in a DCE-based environment. "Combined with DCE developers kits soon to be available for other important platforms, application developers now have the freedom to work on the platform of their choice," said Jonathan Gossels, business area manager for the OSF. "Applications ported now to DCE will be able to take advantage of a large DCE market when major system vendors begin volume shipments of the DCE." Gartner Group Inc. predicts a major proliferation of client/server computing, with the DCE as the catalyst that provides a "vendor-neutral, comprehensive and `industrial strength' package of licensable software." The DCE Developers Kit includes the "core" DCE components necessary for early application development: Remote Procedure Call (RPC); Threads; Cell Directory Service (CDS); and Security services. Other standard DCE components which are less crucial to the initial porting and development of distributed applications, such as the Distributed File Service (DFS) and the Global Directory Service (GDS), are not included in the Developers Kit. The DCE Developers Kit is available as a bundled package, priced at U.S. $15,000. Licensees may operate one Name Server, one Security Server, and up to 10 DCE clients on either supported platform. Support is bundled for one year, and includes an update based on DCE 1.0.1, plus telephone support for troubleshooting and bug reporting. Documentation and training are also bundled, including two seats in a two-day application developers course delivered by Transarc. Additional Server licenses may be purchased for $2,000 each, and additional client licenses for $500 each. Additional training may also be purchased for $750 per seat. Transarc is currently accepting orders for the DCE Developers Kit. Early licensees of the DCE Developers Kit will include companies developing applications using Encina, Transarc's DCE-based family of online transaction processing (OLTP) products. Using the DCE as its foundation, the Encina Toolkit extends the DCE to support the transaction model. All other Encina products, including the Encina Monitor and the Encina Structured File Server, use the Encina Toolkit as their foundation and provide additional functionality required for OLTP. "Participants in Transarc's Early Availability Software (TEAS) program --- a distribution program for early access to Encina products --- rely heavily on both Sun SPARCstations and IBM RS/6000s as development platforms," according to John Schiller, strategic marketing manager for Encina. "Providing the DCE Developers Kit on both of these platforms enables us to meet the needs of our customers in a timely way." First product ship for Encina is scheduled for the first quarter of 1992. With this announcement, Transarc continues its role as a leader in DCE technology. Transarc was a member of the original "DEcorum" partnership that proposed what was to become the fundamental DCE architecture. As a technology supplier to the OSF, Transarc provides the key data management components of the DCE: the Distributed File Service (DCE-DFS), and the Local File System (DCE-LFS), a log-based physical file system for fast server restart. Transarc Corporation is a developer of open distributed systems software, employing over 100 employees in its Pittsburgh headquarters. The company's products focus on two main areas of distributed computing --- file systems and transaction processing. Transarc's first major file systems product, AFS 3, is currently licensed by more than 200 sites in 15 countries worldwide. Early licensees of Transarc's Encina product include Charles Schwab and Citibank. Transarc continues to invest in the development of software products which will expand the functionality of the DCE. # # # AFS is a registered trademark and Encina is a trademark of Transarc Corporation. Other brands and product names appearing herein may be trademarks or registered trademarks of third parties. For more information contact: Transarc Corporation The Gulf Tower, 707 Grant St. Pittsburgh, PA 15219 412-338-4400 412-338-4404 FAX brink@transarc.com Note: Customers should be informed that the threads package included in the Transarc DCE Developers kit is not based on the CMA threads that were selected by OSF DCE and part of the G.A. level IBM DCE product. Therefore, extensive application prototyping using the Transarc threads package is not recommended. ====================================================================== >(U)92070. 3.1 server for 3.2 install To use a 3.1.5 system to netinst 3.2, get hold of the file /usr/lpp/bosinst/scripts/sendfile from a 3.2 system and place it in the /u/netinst/scripts directory on your server, and try again. ====================================================================== >(U)92071. ISPF/PDF Dialog on the AIX Company: Dynasoft Corp. Address: 6300 N. River Rd. Rosemont, IL 60018 800-332-3962; 708-696-4450 FAX: 708-696-2277 ====================================================================== >(I)92072. Some CATIA tips for 3.2 From: Frank Kraemer Sub.: CIPP meeting no. 3 - AIX 3.2 & CATIA doc The third CIPP (CATIA Installation Productivity Project) workshop was help in the german education center last week. We worked on the following topics: * AIX 3.2, installation, set up * AIX 3.2 LPP list for CATIA * AIX 3.2 filesystems sizes * Running CATIA under AIX 3.2 * Disk space requirements for CATIA V3R2MR3 * Plotting under AIX 3.2 * CATIA Performance test * AIX 3.2 Diskless set up * Installation of CSM/CSMA under AIX 3.2 * Network test results * Network set up we compiled a script file named CIPP92 LIST3820 with the results. This script is available from AIXDOC with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET CIPP92 LIST3820 or TOOLS SENDTO DALVM41B IBMPC AIXDOC GET CIPP92 LIST3820 frank :-) ====================================================================== >(U)92073. GCC 2.0 formally released| >From USENET. Note that debugging information for the 6000 is NOT generated, so this will apparently be useless for developing new code (but might be useful for porting existing code written with GCC on some other platform). The words of the Stallman have been censored in the announcement below. "They" made me do it. | From: rms@gnu.ai.mit.edu (Richard Stallman) | Newsgroups: gnu.gcc.help,gnu.gcc.announce,gnu.g++.announce | Subject: GCC 2.0 released | Message-ID: <1-9202220854.AA25765@mole.gnu.ai.mit.edu> | Date: 22 Feb 92 08:54:57 GMT | | People have been waiting for GCC 2.0 for a year. Now it's | available for anonymous ftp from /pub/gnu/gcc-2.0.tar.Z | on prep.ai.mit.edu. There are no diffs from version 1--such | diffs would be too large to be useful. | | | Version 2 of GCC can generate code for the IBM PC/RT, the IBM SR/6000, | the Motorola 88000, the Acorn RISC machine (not fully tested), the AMD | 29000 and the HP-PA (700 or 800), in addition to several machines | supported by version 1 (Motorola 68000, Vax, Sparc, National | Semiconductor 32000, Intel 386 and 860, and Mips). Ports for the IBM | 370, the Intel 960, the Clipper, the Tron (a Japanese standard | computer architecture) and the NCUBE are on their way, but there is no | estimate of when they will be available. Note that using GCC to | compile for the HP-PA requires as yet unreleased versions of other GNU | software such as the assembler and linker. | | Version 2 can generate output files in a.out, COFF, ECOFF, ELF, XCOFF, | VAX-VMS and OSF-Rose formats when used with a suitable assembler. It | can produce debugging information in several formats: BSD stabs, COFF, | ECOFF, ECOFF with stabs symbols, VAX-VMS and DWARF. (We may support | XCOFF for the SR/6000 in the future.) | | Version 2 can be easily configured as a cross-compiler, running on one | platform while generating code for another. | | Version 2 supports compatible calling conventions for function calling | and return values on the Sparc (unlike version 1) as well as the other | machine types. | | Early testing of GCC Version 2.0 indicates that it produces faster | code for SPARC computers than Sun's latest released compilers (both | bundled and unbundled). It is also the fastest known compiler for | the Motorola 88k. | | | In addition to ANSI C, GCC Version 2.0 includes support for the C++ | and Objective C languages. Objective C is an object-oriented language | which adds to C features similar to Smalltalk. The front end for the | Objective C language was donated by NeXT Computers, Inc., which uses | GCC as the basis for their NeXTstep operating system. (Run-time | support for the Objective C language is still under development.) | | GCC extends the C language to support nested functions, non-local | gotos, taking the address of program labels, and unnamed structures as | function arguments (among other things). There are also many new | warnings for frequent programming mistakes. | | GCC Version 2 can produce position-independent code for several types | of CPU: 68000, 88000, 80386, Sparc, and SR/6000. Supporting PIC on | additional suitable CPU types is not too difficult a task. Sam Drake / IBM Almaden Research Center ====================================================================== >(I)92074. GCC 2.0 formally released| - the internal version More about GCC 2.0 on the 'SR/6000': A prerelease package of GCC 2.0 and GDB, with debugging enabled, does exist for the Risc 6000. Internal users can get a copy from me following consultation with local IPL and concurrence of local management. I can also help account reps who have ISV's, BP's, or customers who require Gnu tools. The released GCC 2.0 lacks debug support because of two problems that are being or have been fixed. First, the AIX assembler had numerous problems with debug pseudo-ops; second, the differences between COFF and XCOFF debugging interfaces meant that GCC's XCOFF debug output was not integrated into FSF source until just a few days ago. A fixed assembler is now available from Austin as an separately- installable emergency fix for APAR IX22829. Knowing that a working assembler is available, FSF expects to distribute a working debug interface with their first revision of GCC 2.0 in about a month. That at least was the last news I've had. Larry Breed ====================================================================== >(I)92075. Installation of an IBM OEM 1 GB disk The disc mentioned here is only available through IBM OEM channels. It is not available through standard IBM sales offices. From: Frank Kraemer ++++++++++++++++++++++++++++++++++++++++++ 0.) Info: I removed all internal disks of my RS-320 and installed one IBM 1 GB disk. (The maximal number of disks would be 2.) For AIX 3.2 the 1 GB disk is a "Other Suppliers Disk". The target of the test is to valide that the system can be installed and boot fine using AIX 3.2. Thanks a lot to Bernard Zeller from CE Mainz - due to his excellent knowledge things were running after a short time. 1.) Installation: I booted the system from a 1/4" tape. The "Install Screen" came up. I selected the line "1 - Install AIX". The system showed the message: >"No disk found for installation" 2.) Trace disk status: Select "4 - Perform Maintenance" on the "Install Screen". The system will show a message like "enter getroofs .....". There is no root filesystem on the disk - do not run this command. a) Test if the disk is configured in the ODM Enter: odmget -q "name=hdisk0" CuDv >CuDv: > name = "hdisk0" > status = 1 > chgstatus = 0 > ddins = "scdisk" > location = "00-01-00-00" > parent = "scsi0" > connwhere = "00" > PdDvLn = "disk/scsi/osdisk" b) Test if the disk is flagged as "available" Enter: lsdev -C -c disk -S Available -F "name location subclass" >hdisk0 00-01-00-00 scsi c) Test the IPL information Enter: ipl_varyon -i >PVNAME BOOT DEVICE PVID VOLUME GROUP ID >hdisk0 NO 00000814a1716010 not defined 4.) Create the volume group 'rootvg' on the disk: Enter: mkvg -f -y rootvg -s 4 -d 1 hdisk0 >rootvg 5.) To be shure the 'rootvg' works fine add the 'boot' logical volume: Enter: mklv -y hd5 -t boot -a e -r n rootvg 3 hdisk0 >hd5 6.) The disk has now the right informations - and we start from beginning .......so just press the yellow button twice. 7.) Installation: The "Install Screen" will come up again. Select the line "1 - Install AIX". The location of the 1 GB disk was displayed fine. Installation was possible without an error. 8.) Statistics: After rebooting in key position "normal". a) Test if the disk is configured in the ODM Enter: odmget -q "name=hdisk0" CuDv >CuDv: > name = "hdisk0" > status = 1 > chgstatus = 2 > ddins = "scdisk" > location = "00-01-00-00" > parent = "scsi0" > connwhere = "00" > PdDvLn = "disk/scsi/osdisk" d) Test the IPL information Enter: ipl_varyon -i >PVNAME BOOT DEVICE PVID VOLUME GROUP ID >hdisk0 YES 00000814a1716010 00002849c118eb6d e) Test disk statistics Enter: lspv hdisk0 >PHYSICAL VOLUME: hdisk0 >PV IDENTIFIER: 00000814a1716010 >PV STATE: active >STALE PARTITIONS: 0 >PP SIZE: 4 megabyte(s) >TOTAL PPs: 239 (956 megabytes) >FREE PPs: 197 (788 megabytes) >USED PPs: 42 (168 megabytes) >FREE DISTRIBUTION: 44..32..25..48..48 >USED DISTRIBUTION: 04..16..22..00..00 >VOLUME GROUP: rootvg >VG IDENTIFIER 00002849c118eb6d >VG STATE: active/complete >ALLOCATABLE: yes >LOGICAL VOLUMES: 9 >VG DESCRIPTORS: 2 frank :-) ====================================================================== >(U)92076. loading kernel extensions and getting nasty returns. Be warned, youse guys, ..... 3.2 does things differently||. It looks like the compiler defaults have changed a little SO if you had cc -o thing -ethat_thing ......... in your makefile when making a kernel extension, AND if when compiled under 3.2, you get nasty returns trying load the extension, when you did not under 3.1.5 THEN include -bloadmap blugh as a compiler option go look in the load map blugh see if there is any mention of libc.a or any other library that you dont want in a kernel module If there is then you are picking up the wrong versions of syscalls and the like ... and when you do a K_LOAD it will barff. I am presuming that this is a result of differing compiler (cc) defaults between 3.1.5 and 3.2 ... I have seen related garbage when compiling my favorite goodies ... they gave me error/warning messages, again because compiler defaults changed. The solution is to use:- cc -c to get .o files and then use a specific ld operation with specific libraries et al. cheers pete saruman@watson ====================================================================== >(I)92077. FDDI performance As far as AIX 3.2 TCP/IP support for the FDDI interface goes, it should take full advantage of the default 4352 MTU. I believe that 4352 is the maximum MTU supported by any standard FDDI adapter. AIX 3.2 TCP will support a window size of 64K but most of my TCP throughput tests show that a window size of 56K is better for overall TCP performance for both FDDI and SLA (however, for SLA socket writes <= 1K, a 16K window should be used). You can set this for applications like ftp, rcp, etc... by issuing; "no -o tcp_sendspace=57344 -o tcp_recvspace=57344" as root. Be carefull with the no command as this will cause more mbuf usage per TCP connection active on your system. Here are some 3.2 performance numbers. --------------------------------------- TCP Socket throughput test for FDDI, SLA interface, memory to memory. Throughput KBytes/s Data Size Wrt BufSize FDDI SLA 8192000 128 543 543 8192000 1024 2280 1750 8192000 4096 3941 5485 8192000 8192 4754 5157 8192000 28672 5105 7459 8192000 57344 5118 5062 ------------------------------------------- Peak KBytes/s 5160 7561 Average KBytes/s 3623 4242 Normal peak throughput 1.00 1.47 Normal mean throughput 1.00 1.17 1 Note: 9202 FDDI with default mtu, Socketbuffs 56K. 1 System: RiscSystem 6000 530H->530H. 2 Note: 3.2 GOLD SLA, default mtu, Sockbuffs 56K except 128/1024 used 16K. 2 System: RiscSystem 6000 530H->530H . Both FDDI and SLA are restricted by many factors such as memory copies, CPU bandwidth, and cache misses. Throughput improves by approx 3.1% for each additional MHz CPU speedup. Unfortunately, I do not have 550 numbers but I will try to get them. In addition, SLA would probably see improvement when TCP allows window scaling which is being considered for a future release. As an aside, our FDDI performance is quite good as compared to the DECstation 5000/200 running Ultrix4.1. A 530 can transmit data twice as fast as the DEC can. Will Fiveash, Performance Dept. D29, "My opinions above, facts below." Internet: fiveash@perfmap.austin.ibm.com VNET: FIVEASH AT AUSTIN TIE: 678-7904 ====================================================================== >(I)92078. /6000 configurator for the PC in Germany Den Konfigurator bekommt man mit TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET(or SUB) KONFIG6K oder REQUEST KONFIG6K FROM AIXINFO AT MUNIVM4 Hinweise zum Konfigurator RS/6000 auf PC & PS/2 (File KONFIG6K EXEBIN): - bin{r auf PC oder PS/2 herunterladen - auf dem C-Drive ein Subdirectory CFRS6K einrichten - KONFIG6K.EXE in das Subdirectory CFRS6K kopieren - Subdirectory CFRS6K zum aktuellen Directory machen - die EXEC KONFIG6K aufrufen - es entstehen 7 Files, darunter: CFRS6KGR.EXE CFRS6K.HRD CFRS6K.SFT ZUMLESEN - in ZUMLESEN ist dann eine detaillierte Bedienungsanleitung - Aufruf des Konfigurators: c: cd cfrs6k cfrs6kgr Dieser Konfigurator wird als ein Versuch zur verbesserten Feld- unterst}tzung zur Verf}gung gestellt. Ob er eine bleibende Einrichtung und ein Standard-Output der IBM Produktentwicklung wird, h{ngt u.a. von der Feldakzeptanz ab. u~ern Sie Ihre Meinung und geben Sie diese sowie R}ckfragen und Hinweise an Hr. Dr. Krieg 918-5389, STUTVM3(GKRIEG) ====================================================================== >(U)92079. O'Reilly & Associates (Nutshell Books) Catalogue I just received one of O'Reilly & Associates 'mini-catalogs'. They have a new service, or at least new to me, of forwarding their latest information via e-mail to subscribers. I subscribed yesterday and had a confirmation this morning along with an outline and example source code sites for their new RPC book. To be added to their mailing list, send a note to: book-info-request@ora.com Richard L. Mayson ====================================================================== >(U)92080. SCSI MICROCODE INSTALLP DISKETTE (long post) Hello AIX users, This post concerns the new microcode update diskette, also known as EC------. I'll go into a little background information first. The diskette contains the system files: /etc/microcode/8d77.32.04 /etc/microcode/8d77.42.02 /etc/microcode/8d77.44.02 /etc/methods/cfghscsi /etc/methods/cfgchk The 8d77.xx.yy files are obviously downloadable microcode files. Which file gets down loaded depends on the "xx" hardware level of your particular SCSI card. The cfghscsi and cfgchk files already exist on your system. The cfghscsi file is the executable which configures the SCSI card to your system. The cfgchk file does a last minute check on your system after all the cards have been configured. It points out any potentially bad cards or configurations. Anyway, the installp command downloads these files into their directories, does a checksum on the files, edits the file /usr/bin/blv.proto and then does a "bosboot -a" to the system. When you do a bosboot for your system, it rebuilds the boot image. The idea in this case was to include the new microcode files and cfghscsi into the sytems boot image. The cfgchk file is not considered essential for the initial bringup of the system, so it is not included to keep the boot image small. The bosboot command takes the /unix and all the files listed in /usr/bin/blv.proto and builds the boot image. Then when you reboot, your system comes up with that new boot image. Please note, on the average customers don't do that many bosboots each year. Usually it is after applying a PTF, kernel fix, or as part of repairing a system. Thus, you can go through many shutdowns and reboots (due to power surges, program crashes, or maintenance calls) and be booting off an image that is several months old. Three weeks ago, the Austin site began receiving some calls from the field from people having trouble rebooting their systems after running Three weeks ago, the Austin site began receiving some calls from the field from people having trouble rebooting their systems after running the installp. Since it is our responsibility to ensure that we don't cause you to corrupt your system, we immediately agreed that a flash should be sent out to the field not to run the installp until it was determined what caused some systems not to reboot. The most common symptom was the machine hanging on the 552 LED upon reboot. This flash was not an indication that we knew what the problem was, we just wanted to contain any more possible damage. A lot of people took this flash to mean that the diskette was just plain no good. Let me state right now, that is not case. Immediately, we started trying to recreate this problem. Since we were very sure that the microcode itself could not cause this type of problem and the cfgchk file can't cause the 552, we assumed that it was the cfghscsi file that was causing the problem. Thus, we were advising customers to replace the cfghscsi file on their disk with the one on the install/maint diskettes. All install/maint diskettes contain the cfghscsi off of the machine which they were cut. Since, some people in the field reported coming up (with some other problems), we assumed that was the culprit. But, that did not tell us what was the CAUSE of the 552. >From all the data assembled, we have concluded that the installp diskette is not the cause of the boot problems some customers have seen. Of all the customers that have gone ahead and run the installp, just a handful have actually experienced any problems on reboot. We believe that the cause of the reboot problem was that the system was subtlely corrupted in another manner which was brought out with the installp. The following is an explaination of the bosboot process by my level 3 software cohort, Julie Levell: A bosboot command will build a boot image with the files that exist in your current filesystem. A phase 1 RAM file system (see /usr/bin/blv.proto) and the kernel (/unix) are put together into a file system image and dd'ed to the boot logical volume (hd5). At the end of this image there is a packed configuration database (savebase) that is restored into the RAM filesystem at boot time. The bosboot command will also update the boot record at the front of the disk with "pointers" to the physical location on the disk that the boot logical volume resides. The bosboot command will (optionally) rebuild the bootlist in NVRAM, which is the list that ROS reads to determine which disk to boot from. However, during our debugging of this problem, we figured out that we left the install documentation incomplete (my fault). Great care must be taken when installing it onto a 3.1.0 system (anything under the 3005 level). The cfghscsi is NOT compatable with the databases at that level. We will be lifting the freeze on installing the microcode diskette. However, below are some new notes that will replace the install instructions. They will cover what to do for the 3.1.0 systems. Additionally, we are asking people to run a bosboot onto their system BEFORE the installp (and then rebooting) to verify that their system would have come up anyway. This ferrets out any hidden corruption that can not be blamed on the installp diskette. Here are the instructions: ____________________________________________________________________________ Microcode Installation Instructions This package contains a 3 1/2 inch microcode diskette. The microcode contained on this diskette is required to fix a data miscompare problem that could occur with the SCSI I/O controller when doing a READ from tape that has variable length records. At the end of the installation of the microcode into the operating system, the microcode diskette is to be placed with the diagnostic diskettes and left with the customer. If a Preliminary version of this code had been previously installed, find the preliminary diskette and discard it as this new version incorporates several changes. These instructions were modified 2/17/92 to resolve problems that resulted when installing this microcode. Installation Procedure You must be the root user to install this package. The key must be in the normal position. 1. Verify free space by entering the following command: df /tmp If you have 7500 KB free space, proceed to step 2. If you do not, before you proceed, you must increase the free space to 7500 KB either by deleting unwanted files or by adding space using "smit" as follows: To increase the size of the /tmp directory, enter: smit jfs Select: Change / Show Characteristics of a Journaled File System Select: /tmp Select: Size of file system(in 512 byte blocks) Enter the new file system size in the field provided Press ENTER to execute the command 2. Inquire on which physical disk the boot logical volume resides by entering the following command: lslv -m hd5 Your system will respond with hdiskX where X is the number of the boot logical volume. Substitute the value of X that your system supplies into the following commands wherever hdiskX is used. 3. Enter the following command: bosboot -a -d /dev/hdiskX -l /dev/hd5 -u 4. Reboot by entering: shutdown -Fr This will take awhile. Please be patient. If any errors occur try your normal recovery techniques; if this does not work call your local IBM Software support organization for assistance. If no error occurs, proceed with step 5. 5. If your machine is running AIX 3.1.5 (ACTIVE service release level of 03.01.0005.00xx) or higher go to step 6. If you are unsure of the ACTIVE service level of your system use the following command: lslpp -h bos.obj If your machine is running AIX below level 3.1.5 execute the following command: cp /etc/methods/cfghscsi /etc/methods/orig.cfghscsi 6. Insert diskette into drive. 7. Enter the following command: installp -Fq all 8. If your machine is running AIX 3.1.5 or higher go to step 9. If your machine is running AIX below level 3.1.5 execute the following: cp /etc/methods/orig.cfghscsi /etc/methods/cfghscsi 9. Enter the following command: bosboot -a -d /dev/hdiskX -l /dev/hd5 -u 10. Reboot by entering: shutdown -Fr This will take awhile. Please be patient. 11. To verify that the code was properly loaded, enter the following command: lsattr -E -l scsi0 -a ucode (NOTE: If your system does not have a scsi0 controller then use scsi? in this command, where ? is the number of one of the scsi controllers in your system) If the system responds with one of the following, the down load occurred properly: ucode/etc/microcode/8d77.32.04 Name of adapter code download file False ucode/etc/microcode/8d77.42.02 Name of adapter code download file False ucode/etc/microcode/8d77.44.02 Name of adapter code download file False Problem Reporting For problem reporting, contact your local IBM Software support. From: shieh@racerx.austin.ibm.com ====================================================================== >(I)92081. Internet Technology Handbook From: vivian@sparky.nisc.sri.com (Vivian Neou) Newsgroups: misc.books.technical Date: 28 Feb 92 00:03:53 GMT Organization: SRI International Originator: vivian@sparky SRI International is pleased to announce the publication in February 1992 of the new Internet Technology Handbook, a six volume set of the most comprehensive collection of current Internet documentation available in hardcopy. SRI and the Handbook's consulting editor, Dr. Vinton Cerf, evaluated the more than 1250 RFCs that have been issued and have chosen those most pertinent to today's networking technology and trends. We categorized and organized this core set of RFCs into ten networking topics. Each topic is treated in a different section of the Handbook; each section contains an introductory explanation of the topic, summaries of the RFCs that pertain to the topic, and the full text of each RFC. The Handbook includes all the current Internet standard protocols as defined in RFC 1250. In addition, many RFCs that provide supporting information, experimental protocols, or Internet policy are included to give the most complete picture of internetworking possible. We've done the work of organizing everything so you can have complete information, clearly presented. One year of free updates are included with the handbook. On a quarterly basis, SRI reviews all new RFCs and chooses the most pertinent. These RFCs are then organized for inclusion in the handbook, and provided to handbook owners. The Internet Technology Handbook covers: ITH Volume 1 Introduction to the Internet Internet Organization and Policies: Internet Activities Board Registered Information U.S. Government's Role Architectural Model and Requirements The Current Internet High-speed Networking ITH Volume 2 Network Interface Layer Protocols ARP, RARP and Bootstrapping IP over Network Interface Layer Protocols Internet Layer Protocols Internet Layer Protocols Functions and Algorithms Subnetting Broadcasting and Multicasting OSI Coexistence ITH Volume 3 Routing Architecture and Requirements Intra-Domain (Interior Gateway Protocols) Inter-Domain (Exterior Gateway Protocols) Transport Layer Protocols Internet Transport Layer Protocols TCP Functions Performance and Implementation OSI Coexistence ITH Volume 4 Monitoring and Management Network Management Policy Architectural and Protocol Features Management Information Bases Network Management Operations ITH Volume 5 Utility Protocols Presentation Services Directory Services Time Protocols Remote Procedure Calls Network Access Protocols File Transfer Protocols File Access Protocols Miscellaneous Utilities ITH Volume 6 Application Protocols Electronic Mail Security Miscellaneous Applications Although individual RFCs are available on-line on the Internet, the Internet Technology Handbook makes available all the most important RFCs in hardcopy and is compiled and organized with introductory information for each RFC. The ITS may be ordered as a package with SRI's TCP/IP networking CD. The TCP/IP CD-ROM provides the most comprehensive and up-to-date source of technical information on the Internet. The CD includes all the online Requests For Comments (RFCs) and For Your Information documents (FYIs, a subset of the RFCs) issued through February 7, 1992. It also includes all online Internet Engineering Notes (IENs), the GOSIP specifications, as well as other protocol, security, and miscellaneous Internet information files. In addition, it provides archives of Internet technical mailing lists that discuss protocol implementation issues. As a bonus, the CD includes networking source code that is freely available from various Internet sites. Included for the first time on the CD is source code for the X window system (version 11, release 5). The CD features a search program, which is linked to an index for the technical documents that are included on the disk. This program makes it easy to find the appropriate technical document for your needs. An executable version of the search program for IBM PCs and SunOS Sparcstations is on the disk, and Unix/C source code is also included for other systems. The new release is compatible with Macintoshes as well as PCs and Unix based systems. The TCP/IP CD is an ISO-9660 (High Sierra) format compact disk. ASCII files are formatted for Unix, Macintosh and MS-DOS systems and may be readable on other systems supporting ISO-9660 filesystems. The list price for the six volume, 7000 page ITH is $785 and the TCP/IP CD lists for $195. The combination is avaliable for $985, and includes two releases of the CD-ROM. For further information, contact SRI International, Network Information Systems Center, 415-859-3695; fax, 415-859-6028 or via e-mail at NISC@NISC.SRI.COM. Information for Japanese orders may be obtained from Forval Creative Inc., 81-3-5800-2831 or fax, 81-3-5800-5960. From: WHEELER at ALMADEN ====================================================================== >(I)92082. NCS - configuration/info From: Frank Kraemer Sub.: NCS - configuration/info Note: found in NCS Ref. Manual ISBN 0-13-617085-4 (Apollo/HP doc) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2.6.1 Location Broker Software: ===== The Local Location Broker (LLB) is a server that maintains a database of information about objects and interfaces located on the local host. The LLB runs as the daemon llbd. The LLB provides access to its database for application programs and also provides the Location Broker forwarding service. An LLB must run on any host that runs NCS servers. The Global Location Broker (GLB) is a server that maintains information about objects and interfaces throughout the network or internet. There are two versions of the GLB daemon: glbd and nrglbd. The two versions provide the same functionality to clients, but glbd is replicatable, while nrglbd is not. We (Apollo) provide glbd only for Apollo, SunOS, and ULTRIX (DEC) systems :-( :-(. For other systems (such as AIX), we (Apollo) provide nrglbd. The Location Broker Client Agent is a set of library routines that application programs call (such as CATIA) call to access LLB and GLB databases. When a program issues any Location Broker call, the call goes to the Client Agent at the local host. The Client Agent performs the actual remote lookup or update of infromation in the appropriate Location Broker database. 2.6.2 Location Broker Data: ===== Each entry in a Location Broker database contains information about: * an object * an interface * the location of a server that exports the interface to the object Field: Description: ---------------------------------------------------------------------- 1 Object UUID : unique id of the object 2 Type UUID : unique id that specifies the object type 3 Interface UUID : unique id of the interface to the object 4 Flag : indicates wheter the object is global 5 Annotation : 64 characters user defined data 6 Socket Address Lenght : sizeof(Socket Address) 7 Socket Address : location of the server that exports the : interface to the object ---------------------------------------------------------------------- 2.6.4 The Location Broker: ===== The LLB manages information about servers running on the local host. It also acts as a forwarding agent for remote procedure calls. The forwarding facility of the LLB eliminates the need for a client to know the specific port that the server uses and thereby helps to conserve well-known ports. The LLB listens on one well-known port per address family (it is just 1 := IP for AIX). It forwards any messages that it receives to the local server that exports the requested object. Forwarding is particulary useful when the client requesting a service already knows the host where the server is running. The server can use a dynamiclly asssigned opaque port (number 1024 to 5000); it needs to register only with the LLB at its local host, not with the GLB. To access the server, the client needs to specify the object, the interface, and the host, but not a specific port. 2.6.5 The Global Location Broker: ===== The GLB manages information about servers running anywhere in the network or internet. Clients typically lookup calls to the GLB when they do not know at which host a server is running. 3.1.4 Loction Broker Administrative Tools: ===== NCK includes utilities that administer the Location Broker: lb_admin, the Location Broker administrative tool, and drm_admin, the Data Replication Manager administrative tool. The lb_admin tool allows you to inspect or modify the contents of a Location Broker database. It provides lookup, register, unregister, and garbage collection operations. It can perform these operations on any LLB or GLB database. The drm_admin tools manages the replication of the GLB database. It can inspect or modify replica lists, merge databases to force convergence among replicas, stop servers, and delete replicas. It does not look up, register, or unregister database entries. Note that we (Apollo) do not supply drm_admin for systems that use nrglbd (as AIX does), the non-replicatable version of GLB daemon. 5.3.2 Managing RPC Handles: ===== (A) (B) (C) (D) ************** ***************** ***************** ***************** * No Handle * * Unbound * * Bound to Host * * Fully Bound * * * * Handle (for * * Handle (for * * Handle * * * * broadcasting) * * forwarding) * *---------------* * * * * *---------------* * port * * * *---------------* * host * * host * * * * object * * object * * object * ************** ***************** ***************** ***************** From: To: Via: Comment: ------------------------------------------------------------- A B rpc_$alloc_handle() : -none- A C rpc_$bind() : with unspecified port A D rpc_$bind() : with specified port B C rpc_$set_binding() : with unspecified port B D rpc_$set_binding() : with specified port C D rpc_$set_binding() : with specified port 18.332 /etc/ncs/glb_sites file: ===== The glb_sites file lists the network addresses of hosts where Global Location Broker (GLB) daemon may be running. Ordinarily, programs contact a GLB by broadcasting on the local network. However, some systems do not support broadcasting. Also in certain internet configurations, not every network can have a GLB. (This typically occures in internets that use nrglbd, but it can also occur in an internet that uses glbd if not all networks include a host that run a glbd.) For hosts that cannot locate a GLB via broadcast, the /etc/ncs/glb_sites file provides a list of addresses where the host can try to directly contact a GLB. Each line in glb_sites contains a network address where GLB may be running. Hosts that have a glb_sites file try these addresses in order. Each address has the following form: : e.g. ip:master.xyz.austin.ibm.com If a host has a glb_sites fiel but does not find a GLB at any of the addresses listed in the file, the host then tries to locate one via broadcast. ===== frank :-) :-) ====================================================================== ====================================================================== working as designed: IBM adj. 1. In conformance to a wrong or inappropriate specification; useful, but misdesigned. 2. Frequently used as a sardonic comment on a program's utility. 3. Unfortunately also used as a bogus reason for not accepting a criticism or suggestion. At IBM, this sense is used in official documents| See BAD. >92.03.10 Table of contents: (U)92083. O'Reilly Book about X11 Release 5 (U)92084. Configuring AIX licenses (again, but shorter) (I)92085. "OPEN SYSTEMS TODAY", MARCH 2, 1992 ARTICLE ON NETWARE FOR AIX/6000 (U)92086. How to remove LPPs on AIX 3.2 (I)92087. AIX VERSION 3 PROTOTYPE PERFORMANCE TOOLS AVAILABLE (I)92088. TCP/IP-connections RISC S/6000 - DOS/Windows 3.0 (I)92089. NEW REVISION OF "RS/6000 - A BUSINESS PERSPECTIVE" BOOK AVAILABLE (U)92090. An explanation of the malloc changes in AIX 3.2 (I)92091. Query: Anyone interested in Facsimile support on the 6000? (I)92092. Query: Anyone interested in Scanner support on the 6000? (C)92093. IBM OS/2 LAN Server Product Positioning (U)92094. HOTW: Avoid beeing logged out by CTRL-D ====================================================================== >(U)92083. O'Reilly Book about X11 Release 5 I just discovered the brand new O'Reilly & Associates X Window System book containing information about Release 5 news: Programmer's Supplement for Release 5 by David Flanagan ISBN 0-937175-86-2 29.95$ in USA Contents 1 Introduction to X11R5 2 Font service and scalable fonts 3 Device-dependent Color and Xcms 4 Internationalization 5 Internationalized text input 6 Resource management 7 Other changes in X11R5 Regards Anne ====================================================================== >(U)92084. Configuring AIX licenses (again, but shorter) You can make an even shorter AIXTIP for configuring the AIC license daemon by telling people to run the script /usr/lpp/aic/aic.obj.config as root. It does everything you tell people to do but doesn't expose them to all the gory details unless they need to be. --marc ====================================================================== >(I)92085. "OPEN SYSTEMS TODAY", MARCH 2, 1992 ARTICLE ON NETWARE FOR AIX/6000 March 3, 1992 The current issue of "Open Systems Today" (formerly called "UNIX Today") has a very favorable article on NetWare for AIX/6000. The product was tested on a RISC System/6000 Model 340 with a pre-release copy of AIX/6000 V3.2. The author compared file transfer times between a NetWare PC client, a native NetWare 3.11 server (on a 386/25 Intel) and NetWare for AIX/6000 on a Model 340. A single client was used in all cases. The results were favorable. The installation process is described, as well as the functionality of NetWare for AIX/6000. It is stated that user of native NetWare would probably not see a difference between a PC NetWare server and this product. The main message of the article is that IBM has done an excellent job on this product. We have "won the race to ship NetWare for UNIX v3.11 on a UNIX system" And we have a product that is "straightforward to install and administer" with performance that "is good enough to satisfy even demanding NetWare users." Reprints of this article will be available in 3-4 weeks. Stayed tuned to the AIX+RS on Natboard for instructions on how to obtain them. Questions on this NATBOARD notice are to be forwarded to: RHQVM21(JUDYSA NOTE: Although the above review is pretty positive, don't start a rush to replace PS/2s by /6000s. There are restrictiosn on the product and it is performancewise not as good as a fully featured 486 server. Check out the environment first and ask in NETWARE FORUM on IBMUNIX if in doubt. afx ====================================================================== >(U)92086. How to remove LPPs on AIX 3.2 Internal users can get the script via AIXTOOLS, check out RMLPP PACKAGE. For those that can't get to AIXTOOLS the script is included in this tip. W A R N I N G: USE THIS AT YOUR OWN RISC||| The RMLPP PACKAGE is simply a shell script to remove installed LPPs (Licensed Program Products) or OPPs (Optional Program Products) from an AIX 3.2 system. It takes a command line argument which is a string that should include some part of an LPP name. For example, rmlpp PHIGS will remove all LPPs that have the string PHIGS in their name. It removes all information about the LPP from the ODM SWVPD databases, and then removes all files that the SWVPD databases think are owned by the LPP to be removed. Like the normal unix rm command, this script is very powerful, and unforgiving. If you remove an LPP, it is really gone. To get it back, you must reinstall it. If you try to remove the BOS, it will do it, with obviously serious consequences. Use it with care. The RMLPP ZBIN file is a compressed shell script, in "binary" format. This means you should download it to your workstation in the "binary mode". If you don't know how to do this, consult some of the forums, and reconsider the use of this package. If you find a bug with the script, please let me know. I'll obviously try to fix it. If you want to discuss it, or flame it, or whatever, I believe the correct place to do this is MISCTOOL FORUM. Mickey Coggins 6 March 1992 ----------------- #|/bin/ksh # # Permanently remove a product from disk and AIX databases # if `whoami` |= "root" ; then echo You must be root to run this script. exit 1 fi if `uname -a awk 'print $1$4$3'` |= "AIX32" ; then echo This script only works on AIX 3.2. exit 1 fi TMP_FREE=`df /tmp awk '$3 | /KB/print $3'` if "$TMP_FREE" -lt 1000 ; then echo There is not enough room in your /tmp directory. echo You need 1000 KB free, and you have only $TMP_FREE KB free. echo Either remove some stuff from /tmp, or use chfs to make it bigger. exit 1 fi ODMDIRS="/etc/objrepos /usr/lib/objrepos /usr/share/lib/objrepos" ODMDIR=/usr/lib/objrepos export ODMDIR if $# -lt 1 then echo usage: $0 lppname lppname ... echo lppname is a string compatible with grep, ie "X11" or "PHIGS" echo typing $0 PHIGS will remove all LPPs with PHIGS in their name. exit 1 fi NAMES=$1 shift while $# -gt 0 ; do NAMES="$NAMES$1" shift done echo "Searching for lpps with egrep "$NAMES"...c" for ODMDIR in $ODMDIRS ; do if | -d $ODMDIR -o | -w $ODMDIR ; then echo $ODMDIR is not writeable or is not a directory. echo I hope this is because you are a /usr client or diskless. echo If you are not a diskless or a /usr client, you should stop. echo "Enter y to continue ->c" read answer if "$answer" |= "y" ; then exit 0 fi fi TMP=`odmget lpp awk -F" '/name/ print $2' egrep "$NAMES"` LPPS=`echo $LPPS $TMP` done  if "$LPPS" = "" then echo "failed.nNo LPP with the name $NAMES detected." exit 1 fi echo ok. for ODMDIR in $ODMDIRS ; do mkdir -p /tmp/rmlpp/$ODMDIR > /dev/null 2>&1 done > /tmp/listOfFilesToRM$$ # truncate temporary file, just in case. echo echo This script is about to attempt to remove an LPP from your system. echo I say attempt, because it could fail. If it fails, you may have echo to at least reload the LPP. Use the "lppchk" command to make sure echo all is well with your system. echo # Loop through all the LPP names found. for LPP in $LPPS do DESCR=none answer="" # find the LPP ids. They will be different in the three SWVPD databases. for ODMDIR in $ODMDIRS ; do # get the lpp id for this ODMDIR (yes, they are different) LPPID=`odmget -q name=$LPP lpp grep lpp_id sed 's/.* = //'` # did we find the LPP? if "$DESCR" = "none" -a "$LPPID" |= "" ; then # all the descriptions should be the same DESCR=`odmget -q name=$LPP lpp grep description sed 's/.* = //'` echo "Delete $LPP, $DESCR?" echo "y or (n) ->c" read answer if "$answer" |= "y" ; then # jump back up to the next LPP name continue 2 fi fi # if there is no DESCR, then we didn't find the LPP. Weird. if "$DESCR" = "none" -o "$LPPID" = "" ; then continue fi SOMETHING_DONE_FLAG=true # Optionally, save the ODM stuff we are about to remove, # in case something goes wrong. The problem is it is difficult # to determine if something really did fail, since these commands # don't return any decent error return codes. odmget -q lpp_id=$LPPID history > /tmp/rmlpp/$ODMDIR/$LPP.history odmget -q name=$LPP lpp > /tmp/rmlpp/$ODMDIR/$LPP.lpp odmget -q lpp_name=$LPP product > /tmp/rmlpp/$ODMDIR/$LPP.product # Get the list of files and links to remove later.... odmget -q lpp_id=$LPPID inventory > /tmp/rmlpp/$ODMDIR/$LPP.inventory awk -F" '/loc/ print $2' /tmp/rmlpp/$ODMDIR/$LPP.inventory sed 's/,/ /g' >> /tmp/listOfFilesToRM$$ odmdelete -o history -q lpp_id=$LPPID > /dev/null 2>&1 odmdelete -o lpp -q name=$LPP > /dev/null 2>&1 odmdelete -o product -q lpp_name=$LPP > /dev/null 2>&1 odmdelete -o inventory -q lpp_id=$LPPID > /dev/null 2>&1 done done if "$SOMETHING_DONE_FLAG" = "true" ; then echo ODM work is done. Now, time to delete files.... # This could be catastrophic if there is a problem. For example, # if the ODM database for an application had / as one of its files. # You be the judge. Here's your rope.... cat /tmp/listOfFilesToRM$$ sort -r uniq xargs rm -rf rm -rf /tmp/listOfFilesToRM$$ echo done. fi # take this line out if you want to save your ODM saved files. rm -rf /tmp/rmlpp exit 0 ====================================================================== >(I)92087. AIX VERSION 3 PROTOTYPE PERFORMANCE TOOLS AVAILABLE March 5, 1992 There are now four versions of the tools available. Changes to the operating system require corresponding changes to the tools. Following is a list of the supported tools packages and the levels of AIX V3 on which they will execute successfully: Package Levels of AIX V3 Supported ======= =========================== TOOLS1 3002 ---------------- 3.1.2 TOOLS2 3003 and 2004 ------- 3.1.3 TOOLS5 3005, 2006 and 2007 - 3.1.5 TOOLS6 3.2 GA -------------- 3.2.0 The tools and supporting documentation may be retrieved from the tools disk by issuing the following command from your VM account: TOOLS SENDTO DALVM41B TOOLS AIXIC GET packageid PACKAGE where packageid is the name of the required package. INSTALLATION PROCEDURES FOR TOOLS6 PACKAGE The following procedures will enable the user to successfully place the 'tarbin' files onto his RISC System/6000 machine: 1. Request the package from the AIXIC tools disk. 2. Transfer the TOOLS6 TARBIN1 and TOOLS6 TARBIN2 files to the RISC System/6000 by whatever method you prefer. Ensure that the transfer is a binary transfer and NO TRANSLATION takes place. On the RISC System/6000, the resulting files should be named 'tools6.tarbin1' and 'tools6.tarbin2'. 3. Execute the following on the RISC System/6000 to concatanate the two files into a third file: cat tools6.tarbin1 tools6.tarbin2 > tools6.tarbin.Z 4. Execute the following on the RISC System/6000 to uncompress the tools6.tarbin.Z file: uncompress tools6.tarbin You should now have the file tools6.tarbin in your directory. 5. Follow the procedures outlined in the README ASCII or README SCRIPT files sent with the package for a complete list of required steps. DESCRIPTION OF TOOLS The AIX V3 Prototype Performance Tools are a powerful set of tools that can be most useful in evaluating and tuning AIX V3 performance and in supporting the SE in his customer support mission. A brief description of each of the tools is provided below. For more detailed descriptions, refer to the accompanying documentation. With the exception of trace, filemon and tprof, all tools are considered IBM Confidential. Filemon and tprof are classified IBM Internal Use Only. Trace is unclassified. Users should adhere to the rules described in the Restrictions section of this file. Trace: The AIX Trace Facility captures a low-level trace of system and user- program events. The AIX V3 kernel subsystems have been instrumented to emit a log of important system events (e.g., I/O completed, page faults, process dispatched, etc.). Users can instrument their pro- grams to emit program event records to the same trace log. Because trace events are timestamped, users get a complete and accurate picture of flow of control and timing during execution of their applications.  Rmap: Rmap is an extended analysis and reporting tool for log data produced by the AIX trace facility. Rmap complements the standard trace report facility (trcrpt) by summarizing the log data in one or more performance reports selected by the user. Tprof: Tprof provides a detailed profile of CPU usage by an application. Tprof is like the standard AIX program profilers prof and gprof, in that it provides an estimate of CPU usage by each routine in a program. Unlike prof and gprof, it provides a CPU profile of all processes running during an application, not just the program of interest. Additionally, it provides a profile down to the source statement level, if the associated C or Fortran source files are available. All this is accomplished with relatively little or no overhead. Tprof is useful to those whose applications are believed to be CPU-bound, and want to know where and why. Svmon: Svmon is a virtual memory monitor. When invoked, it captures a snapshot of the current contents of both real and virtual memory, and summarizes the contents. Svmon is useful to those who wish to determine which processes, or alternatively which segments, are con- suming the most real memory. Rmss: Rmss provides you with a means to simulate RISC System/6000's with various size memories, without having to extract and replace memory boards. Moreover, rmss provides a facility to run an application over a range of memory sizes, displaying, for each memory size, performance statistics such as the response time of the application and the amount of paging. In short, rmss is designed to help you answer the question: How much memory does a RISC System/6000 need to run a given application with an acceptable level of performance? Filemon: Filemon monitors a trace of file system and I/O system events, and reports performance statistics for files, virtual memory segments, logical volumes, and physical volumes. Filemon is useful to those whose applications are believed to be disk-bound, and want to know where and why. Fileplace: Fileplace displays the placement of a file's blocks within a file system. Logically contiguous files may be physically fragmented on disk, depending on the available free space at the time the file is created. Fileplace can be used to examine and assess the efficiency of a file's placement on disk. Lvextend and Lvmake: Lvextend and lvmake perform the same logical volume allocation functions as the 'extendlv' and 'mklv' commands, but provide more precise control over the placement of the logical partitions on physical volumes. Lvedit: Like the lvmake and lvextend tools, lvedit provides precise control over the creation and placement of logical volumes on physical volumes. As an interactive tool, lvedit allows users to view current logical volume placements, make tentative changes to the placements (creating, removing, or extending LV's), and ultimately commit those changes. Netmon: Netmon monitors a trace of system events, and reports on CPU usage, network device-driver I/O, internet socket calls, and NFS I/O. In its normal mode, netmon runs in the background while one or more application programs or system commands are being executed and monitored. When tracing is stopped via a 'trcstop' command, netmon generates all specified reports and exits. RESTRICTIONS All classified tools, as well as the associated documentation, must be labeled appropriately. In the event that they are taken to a customer site, an IBM SE must be present as long as the tools are loaded on the customer's system. The code and associated documentation must be removed when the SE departs. The output of the tools is not classified, and may be left with the customer. QUESTIONS AND COMMENTS Questions and comments regarding the tools should be submitted via EQUAL/ASKQ. ====================================================================== >(I)92088. TCP/IP-connections RISC S/6000 - DOS/Windows 3.0 below you will find our experience concerning connections between DOS, DOS/Windows 3.0 and RISC S/6000 via TCP/IP here in SPOC/VIENNA. During our tests for a project we evaluated some DOS-TCP/IP implementations - we had a lot of effort and would like to share some useful information with others interested in the DOS/PC connection to AIX/server area. This information derived from our tests in our environment and may lead to different results in other environments. Our predefined environment is: Software PC: LAN-Type, Adapters: Server: MS/DOS 5.0 Token-Ring RISC S/6000 MS/WINDOWS 3.0A IBM 16/4 Adapter AIX 3.1.6 IBM LAN SUPP.PGM 1.23 AT-Bus The main requirement of this installlation are sharing of virtual disks between multiple users in a controlled way and to emulate an terminal to the server to access server-applications. In addition the drivers of the TCPIP implementation must allow the sharing of the network-adapter between different protocols (e.g. IEEE802.2, TCP/IP). Programs evaluated, but not installed are IBM TCPIP V2 for DOS due the lack of locking/sharing support, PC/NFS from SUN due the missing T/R support. Products tested are: PC/TCP+ from FTP: **************** A full-implementation of the TCP/IP protocols, needs minimum 80K below 640K. Windows support officially documented. Multi-tasking in Windows brings the PC into various hang-situations, where only rebooting can be done. Missing reentrant coding will be fixed by the next release 2.1, which was scheduled for 3/92 but recently postponed to 6/92. The release under test was PC/TCP 2.05 PL3 and Interdrive 1.1 PL6 (NFS). Supports many different network-adapters and also IBM T/R via ASI directly (IBM LAN Supp.Pgm). We also did not use the standard VT220-emulation for terminal-emulation to the server, but an VT320/VT420 emulator from Persoft using the FTP's API. Conclusion: Locking/sharing supported, availability and stability in our environment very poor. Product comes from DOS-only - WINDOWS-support not really available. Beame & Whiteside: ****************** Very small (size) product, implements locking/sharing and as far as we saw also Windows-support is implemented well. Locking/sharing can be controlled by using an B&W lockd, which comes in source. Main problem of this product are the missing support at the T/R network-adapter side. T/R is only supported via NDIS (MS-specifications, current IBM Lan Supp. Pgm and adapter do not support) or ODI (Novell specification)||| or public domain packetdrivers. Packetdrivers show various problems with hangs - NDIS drivers coming with the product do not allow the sharing of the network-adapter with 802.2, ODI-driver need a lot of memory in addition to the product itself, shares the adapter with other protocols. Ethernet-configurations were reported to us as stable and error-free. Advantage of this package, is an add-on, which allows the B&W product to emulate the FTP's API - therefore programs written for the FTP programming interface can run unchanged. Windows DLL for advanced programming and calling the TCP/IP services from within Windows-programs is missing. Conclusion: Small and smart program, seems to run stable in multitaksing WINDOWS, but instabilities and overhead due the lack of direct support of T/R via ASI. excellent printersupport (both directions) and HFT Terminalemulation available Seems to meet our requirements. Pathway/NFS from Wollongong: **************************** Various products based on a TCP-kernel available, which can be run standalone or together to provide the neede functions. Pathway/NFS support full DOS sharing/locking and way of locking/sharing can be influenced by an shipped public domain lockd. Small and clean setup product, uses directly T/R via ASI (LAN Supp.Pgm) without intermediate layers - adapter sharable. Smallest tested product around 50K used below 640K. Release still under test, so we dont have further informations. Some weakness with the AIX-authorizationflags for files and misinterpretations. DLL available - lets such packages like INGRES WINDOWS/4GL run on top. Release 1.2 in Betatest now - available 4/92. Persofts SMARTerm420 runs on top. Interesting features like TN3270 addon package, which allows TN-GDDM-Emulation available from Wollongong. Conclusion: At this point in time, seems to meet our requirements - further testing still needed, due to short testing-period up to now. ** AUF DIE DAUER HILFT NUR POWER - AIX & RISC S/6000 ** Tom (61822082 at VIEVMA) ====================================================================== >(I)92089. NEW REVISION OF "RS/6000 - A BUSINESS PERSPECTIVE" BOOK AVAILABLE February 12, 1992 IBM Mechanicsburg Has Just Stocked the new 2nd Edition of "IBM RISC SYSTEM/6000 - A BUSINESS PERSPECTIVE" (GA23-2674) published by John Wiley & Sons. This highly successful book has been Updated to include the Model 320H, Model 950, Xstation 130, new graphics adapters including the 7235 POWER GTO, new extension to AIX, and more. This book contains complete information - all in one place - about the RISC System/6000 System Units, options, peripherals, operating systems, and application programs. Also included is a hands-on session with AIX's InfoTrainer for first time users. Finally, hypothetical small, medium, and large businesses are described and then outfitted with the appropriate RISC System/6000 hardware/software configurations to meet their needs. A companion to the highly successful "IBM PS/2 - A Business Perspective" (G325-0400) AND "IBM AS/400 - A BUSINESS PERSPECTIVE" (GA21-9990), this book describes the RISC System/6000 family in a way understandable by business people. Throughout the book, each feature of the RISC System is described in the context of how it helps the user do his job. IBMers, IBM Business Partners, and IBM Customers can also subscribe to receive future updates to these books through SLSS. CHAPTER 1: Introduces the RISC System/6000 family members. Then the technology (architecture, graphics, auxiliary storage, etc.) and functions are explained in non-technical terms. CHAPTER 2: Reviews the options (feature cards, upgrades, etc.) and peripherals (displays, printers, etc.) for the RISC System/6000 family. CHAPTER 3: GUIDES THE NEW USER THROUGH A 'HANDS-ON' SESSION WITH THE InfoTrainer education system. It then describes the basic types of SOFTWARE (APPLICATION PROGRAMS, OPERATING SYSTEMS, AND DEVICE DRIVERS) and how they work together. CHAPTER 4: Describes the basic types of application programs used with RISC System/6000 computers including cross-industry, industry specific, and custom alternatives with examples. CHAPTER 5: Discusses the AIX Operating system. First basic operating system concepts (i.e. batch vs interactive, multi-users, etc.) are defined in non-technical terms. Then AIX and its extensions are described. CHAPTER 6: Covers popular communications configurations in which RISC System/6000's can participate. These include remote terminals, Local Area Networks, and Wide Area (SNA and Non-SNA) Networks. CHAPTER 7: Discusses issues related to the selection of RISC System/6000 hardware and software to meet the needs of both commercial and technical users. Hypothetical organizations (small, medium, and large) are described and then outfitted with the right RISC System/6000 hardware and software to meet their needs. Then some other planning topics including identifying costs, identifying benefits, lease vs purchase, office ergonomics, and user training are discussed. ====================================================================== >(U)92090. An explanation of the malloc changes in AIX 3.2 AIX V3.2 now offers two allocation strategies to support malloc(), the original 3.1 strategy based on BSD and the 3.2 strategy developed at IBM Yorktown. AIX 3.1 Malloc =------------- The free memory in the heap is organized into a set of 30 buckets. Each bucket points to a linked list of free blocks. The size of the blocks in a bucket are calculated as follows: sz = 2 << (bucket_no + 3) Note that the size requested by the application is boosted by the size of the prefix (8 bytes) which contains heap accounting info. This size, however, is not exactly what ends up getting used. The amount which is actually sbrk()ed is calculated as follows: if (sz is less than a page) amt = page size; nblks = page size / sz else amt = sz + page size; nblks = 1; fi The top half of the if ensures that we acquire small blocks of memory in groups of a page at a time. The "group" of blocks gets added to the linked list for the bucket. Note that since "sz" is necessarily a power of 2, page size is evenly divisible by "sz". The bottom half of the if handles sizes greater than a page. Note that the amount here is increased by a page. This is due to the fact that all blocks greater than or equal to a page are aligned on a page boundary and every block of storage is preceded by a prefix containing heap accounting info. The effect of this is that blocks of storage >= a page in size consume an entire page of storage just for the prefix. A request for 2048 is pathologic since 2048 + 8 bytes for the prefix gets you in the 4096 bucket. Since 4096 >= page size I get an extra page for page alignment which results in 8K allocated for a 2K request| The memory utilization of this algorithm is obviously less than spectacular. First, since the buckets come in sizes corresponding to powers of two, anything between one power of two and another gets lumped together. Yikes|. The rationale is that since this is designed for a virtual memory environment, the pages beyond the actual size of the block will never get touched "and since virtual memory is free..." Second, blocks >= page size eat an extra page for the prefix. I verified that this behaviour is identical with the Berkley behaviour up to the latest level of the Berkley source that I have which is BSD 4.3 Reno sid 5.11. There are a few interesting points to note where AIX V3.1 malloc() differs from BSD. The first is that when sbrk() fails in the BSD malloc, it simply returns a NULL pointer indicating failure. The AIX malloc will attempt to steal memory from larger blocks in the free list. The second is that the AIX malloc ensures that the return address from sbrk() is page aligned at all times. This is due to the fact that the AIX system supports dynamic loading which might affect the break address between calls to malloc. These cases are fringe cases, and I include them here only for completeness. AIX V3.2 Malloc =-------------- In AIX V3.2 a new malloc was incorporated which sported much more frugal memory utilization characteristics. This malloc was developed by Chris Stephenson at Yorktown for his experimental operating system. In this scheme free blocks are organized in the heap in a data structure called a "cartesion binary search tree". In this data structure, free blocks are organized left to right by address, and depth-wise by length. Therefore, the longest node is at the root of the tree, and progressively smaller nodes down from there. The granularity for allocation in this malloc() is 16 bytes. The storage occupied by a block is calculated as follows: sz = ROUNDUP(requested + 8, 16); Therefore, the smallest block is 16 bytes long, and the "wasted" storage is < 16 bytes per block. The other principle enhacement is that freed storage is coalesced with neighbor blocks in the heap whenever possible. This helps reduce fragmentation of the heap. For example, if two 32K blocks are allocated and freed, a 64K block could subsequently be allocated without requiring heap expansion. The previous malloc() would expand the heap to acquire a 64k block since the 32K blocks were not in the bucket for 64K items|. Hope this helps... Tom Tucker IBM PSP Austin, TX. MAIL: tomtomr2.austin.ibm.com ====================================================================== >(I)92091. Query: Anyone interested in Facsimile support on the 6000? From: poist@ibmpa.awdpa.ibm.com (Gregory Poist) I'm looking for people interested in Facsimile support on the Risc System/6000. Please contact me at the address below for more information/discussion. thanks in advance, Greg Poist IBM Personal Systems Programming, Palo Alto POIST at AUSTIN poistibmpa.awdpa.ibm.com UUCP:uunet|ibmsupt|poist VNET:poist at austin ====================================================================== >(I)92092. Query: Anyone interested in Scanner support on the 6000? From: steve@ibmpa.awdpa.ibm.com (Steve DeJarnett) I'm looking for people who are interested in scanner support on the (you know which) 6000. Please contact me offline at the address below for more info/discussion. Thanks in advance, Steve DeJarnett PS Programming, Palo Alto DEJARNET at AUSTIN Steve DeJarnett Internet: steveibmpa.awdpa.ibm.com IBM PSP Palo Alto UUCP: uunet|ibmpa.awdpa.ibm.com|steve (415) 855-3510 IBM VNET: dejarnet at austin ====================================================================== >(C)92093. IBM OS/2 LAN Server Product Positioning IBM Confidential ITSC Austin is sending to this distribution list a file called LANPOS SCRIPT. This paper, IBM OS/2 LAN Server Product Positioning, provides a competitive perspective of IBM LAN Server 2.0 with Microsoft's LAN Manager 2.1 and the NetWare products. It was written by the Austin LAN Server developers. The document is now classified IBM Confidential but will be re-classified later by development. You can get it from the confidential ICTIPS disk with the following command: TOOLS SENDTO MUNIVM4 AIXTOOLS ICTIPS GET LANPOS SCRIPT ====================================================================== >(U)92094. HOTW: Avoid beeing logged out by CTRL-D The Hint Of The Week section from now on will feature a short hint on some AIX command for all newcomers (and oldtimers who already have forgotten it) How to avoid beeing logged out by an accidential CTRL-D: (this is for Bourne and Korn shell users) put the following line in your .profile: set -o ignoreeof You can not quit your login shell with an accidential CTRL-D anymore, you have to type exit to get out. Note, that this applies only to your login shell. afx ====================================================================== ====================================================================== NOTICE: The entire universe, including this file, may one day collapse back into an infinitely small space. Should another universe later emerge, the validity of this information can not be guaranteed. >92.03.21 Table of contents: (I)92095. REALTIME INTERFACE CO-PROCESSORS FOR POWERSTATION/POWERSERVERS (I)92096. HCON Background Printer Support (I)92097. OpenGL press release issued to wire (U)92098. Mouse performance on PCSIM (U)92099. "What" strings in C sources (I)92100. Blown Fuses on SCSI cards (U)92101. Identifying the machine model via a script (I)92102. NetWare/6000 + DOS 5 + other communications concurrently (U)92103. Potential security exposure with the mkgroup command (U)92104. Free AppleTalk/EtherTalk Interface for the /6000 (U)92105. chfs in AIX 3.2 allows to increment the filesystem size (U)92106. CERT Advisory - AIX uucp Vulnerability (U)92107. A substitute for the missing xmkmf on AIX 3.1 (I)92108. AIXTIPS NEWS now available on DIAL IBM in GERMANY (U)92109. HOTW: Shortcuts to often used paths in the Korn shell ====================================================================== >(I)92095. REALTIME INTERFACE CO-PROCESSORS FOR POWERSTATION/POWERSERVERS Note: These are US announcements, please check locally outside the US. March 13, 1992 Some of the Realtime Interface Co-Processor adapters, Multiport/2 and Portmaster (TM), are to be supported on POWERstation/POWERservers. These products have been announced as RPQs for the RISC System/6000 family of POWERstations and POWERservers and will be available May 29, 1992. RPQ NUMBER TITLE 8A0630 Multiport/2--5M FOR RISC System/6000 8A0631 Multiport/2--1M FOR RISC System/6000 8A0632 Portmaster Adapter/A 1MB 8A0633 Portmaster Adapter/A 2MB 8A0636 Eight-Port RS-232 Interface Board - Multiport/2 8A0637 RS-232/RS-422 Interface Board 8A0638 Eight-Port RS-232 Interface Board - Portmaster 8A0639 Eight-Port RS-422 Interface Board/A 8A0640 Six-Port V.35 Interface Board/A 8A0642 Multiport Interface Cable 8A0644 Six-Port V.35 Cable 8A0645 Eight-Port Cable 8A0647 Eight-Port RS-422-A Interface Board (TM) Trademark of International Business Machines Corporation. Send Questions to Dave Brewster at AUSVMQ(BREWSTER). ====================================================================== >(I)92096. HCON Background Printer Support For those of you who would like to know, the problem where a printer session cannot be run in the background has been fixed (I at least hope so) with APAR ix25076. The HCON update that contains this fix is "hcon february X (as in TEN)", it's been an active month|| The below is the README that is shipped with the update explaining the new procedures for running a printer session in the background. Due to HCON using curses, a new process "e789pr" was added to handle this. Instructions for running the HCON background printer ---------------------------------------------------- The new HCON process for running a printer (LU1, LU3 or Non-SNA DFT) emulation window in the background is e789pr. If the user wishes to see the printer session and does not mind the printer session taking up a window then the session should be run via the normal e789 command. The command line parameters for the e789pr command are as such: e789pr <-D debugfile> <-L columns_per_line> session & The -D flag is the HCON debug option for looking at the flow of the data being sent from HCON to the Host and vice versa. The -L option is a new option that was implemented due to a defect where the number of columns attempted to be printed is greater than 132. If the case is, for example, that a user wanted to print to the 180 column of a 180 column printer then the e789pr command would be invoked using the -L 180 option. This option is only valid for printer column values of GREATER than 132, otherwise the normal means of setting up the column value is used. This flag should NOT be used unless the printer is set up to print greater than 132 columns of data. The session is the HCON session profile being used for the printer emulation. If this session is NOT defined as a printer session, an error WILL occur. The & places the e789pr process in the background. The e789pr command should ALWAYS be run in the background (with the &). IF THE ABOVE IS NOT WHAT PEOPLE EXPECTED, Sorry this is the best that could be done under the circumstances. If changes like this are wanted with HCON, please voice an opinion and we can try are best. Mark -- Mark Grosch IBM T-R: mark@happy.austin.ibm.com AIX Commo Field Quality (c/t) VNET : AUSVMQ(MGROSCH) * Opinion - an idea held with confidence but not proven, In other * words they are mine (not IBMs) and for all you know I could be lying! ====================================================================== >(I)92097. OpenGL press release issued to wire From: Judy Radlinsky/Advanced Workstations Media Relations IBM US, Dept DC6 Zip 274 1133 Westchester White Plains NY 10604 Office 2C-401 Ph: t/l 224-4634, (914) 642-; FAX: 5784 SUBJECT: OpenGL press release issued to wire The following was released to the PR Newswire and BusinessWire services here in the US at 10:40 this morning. (SGI released their overview release earlier today.) Contact: Judy Radlinsky (914) 642-4634 IBM LICENSES SILICON GRAPHICS' OpenGL 3D GRAPHICS INTERFACE WHITE PLAINS, N.Y, March 16. . . IBM today announced that it has licensed OpenGL**, the open 3D graphics technology based on Silicon Graphics'** IRIS Graphics Library** (GL**). IBM has also become the sixth member of the OpenGL Architecture Review Board, an industry forum that guides the future enhancement and direction of the OpenGL graphics application programming interface (API). IBM, which licensed IRIS GL in 1988, intends to provide an OpenGL offering as one of the strategic graphics APIs for its RISC System/6000* family of workstations. There are more than 1,500 applications written to the GL API, including those used for conceptual design, medical imaging, computer animation, scientific visualization and mechanical computer-aided design. "GL has a large applications base for 3D graphics APIs, delivers a rich set of function and is gaining wide support in the industry as an emerging standard," said Robert Swann, director of Graphics Systems for IBM's Advanced Workstations Division, Kingston, N.Y. "Providing OpenGL, along with the PHIGS* API we already offer, will enable IBM to deliver to our customers the broadest range of 3D graphics APIs and applications. We are also pleased to be participating with Silicon Graphics and the other members of the Architecture Review Board in making OpenGL a truly open standard that supports multiple vendor platforms. We look forward to working with them to extend the benefits of OpenGL in the vendor, developer and end user communities." Silicon Graphics announced last fall that it was making IRIS GL available to the industry for general licensing. Licensees can implement OpenGL as an extension to existing native windowing system, such as the X Window System**. IBM was the first vendor to integrate GL with the X Window System. # # # * Indicates trademark of International Business Machines Corporation. ** Silicon Graphics and IRIS are registered trademarks, and GL, IRIS Graphics Library, IRIS GL and OpenGL are trademarks of Silicon Graphics, Inc. ** X Window System is a trademark of Massachusetts Institute of Technology. EDITORS' NOTE: For more information on OpenGL or the OpenGL Architecture Review Board, please contact Rosanne Siino at Silicon Graphics, Inc., (415) 335-1029. ====================================================================== >(U)92098. Mouse performance on PCSIM From PCSIM FORUM: Here are some tips which may help make the mouse more useable. I say "may" because as things stand today there are too many pieces of code involved in the critical path (mouse, AIX device driver, AIXWindows server, sockets, PCSIM client, PC mouse device driver, PCSIM VGA emulation, sockets, AIXWindows server, AIX display device driver). Too much needs to happen from the moment you move the mouse until the image of the mouse pointer moves on the screen. Also, this is a subjective issue, what is acceptable in one application for one user on some machine might not be so for someone else or on some other machine or with some other application. Tips: 1) Try GRAB mode instead of FREE mode. This is selected by specifying "Com1" instead of "com1" in the "mouse" option (notice uppercase "C"). In GRAB mode the mouse will not be released back to AIXWindows until you explicitly detach it. You detach the mouse by holding down the mouse center bottom and clicking the left button. You attach by holding down the mouse center button and clicking the right button. 2) Try -wrap option to xinit. This will cause the AIXWindows pointer to wrap left-right top-bottom on the display. This helps prevent the problem of the PC mouse pointer not moving any further in the direction of a display edge once the AIXWindows mouse pointer (which is not visible when PCSIM is attached to the mouse) has reached that display edge. 3) On AIX 3.2 (PCSIM 1.2) which allows re-sizeable VGA window, keep the window small. The larger the window the more data is sent to update the display. In particular, if you make the window geometry equal to the VGA resolution, you eliminate the resizing overhead. Typically the resolution is 640x480 but this depends on the VGA display mode. 4) Turn off the mouse acceleration in AIXWindows which just exacerbates the problem. The following menu can be added to .mwmrc to conveniently turn mouse acceleration off/on: Menu MouseMenu "Linear" f.exec "xset m 1 1" "Ballistic" f.exec "xset m" And added to the RootMenu in .mwmrc: "Mouse Speed" f.menu MouseMenu 5) If you are using a Microsoft mouse driver (MOUSE.COM), and you have access to other versions of it, try other versions. There are countless versions out there, I don't know why they keep changing. Some versions don't recognize the PCSIM mouse at all because of some timing dependency in the code. ====================================================================== >(U)92099. "What" strings in C sources xlc/cc discards SCCS ids in sources that are not referenced. There are two ways arounfd this. Either reference the strings or use pragmas. Unfortuantely pragmas are not portable as it is left to the implemetor of the C compiler how they are interpreted. Try #pragma comment(user,"@(#)My program") This is what the pragma was made for. There is also: #pragma comment(copyright,"any string") #pragma comment(compiler) #pragma comment(date) #pragma comment(timestamp) See the language reference guide for a complete description. ====================================================================== >(I)92100. Blown Fuses on SCSI cards One fairly large problem in the field is the fuse on the SCSI card blowing. Austin has received many cards back that were pulled because the fuse was blown. This procedure weill be included with every card sent to the field now and is also available on Retain to help issolate the problem. This requires an Ohm meter. ************************************************************************ *** READ ME **** READ ME **** READ ME **** READ ME *** This Problem Isolation Procedure is included in this package to prevent SCSI adapters from being replaced because the fuse on the adapter is blown. This information is also available in Retain tip H033021 SCSI ADAPTER BLOWN-FUSE PROBLEM ISOLATION Before replacing the suspected SCSI adapter, the fuse on the SCSI adapter should be checked. The purpose of this fuse is to protect the internal and external SCSI bus. It can be blown by a cable, terminator, or any device attached to the SCSI bus. The SCSI adapter itself will not cause the fuse to blow and should not be replaced for a blown fuse. 1. *IMPORTANT* Power off the system and all externally attached devices. All of the testing will be done with all devices powered off. It is not necessary to remove the SCSI adapter from the machine or disconnect any cables from the SCSI adapter. Remove the fuse and use a digital OHM meter to check the fuse. If blown, install a new fuse and continue. 2. Locate diode D1 and oscillator Y1. Both are located on the top edge of the adapter: diode D1 is 3/8 inch to one side of the internal SCSI cable connector next to the fuse; Y1 is the square can 2 inches to the other side of the connector. 3. Connect the positive (+) lead of the ohm meter to the cathode of D1 (end nearest the fuse) and the negative (-) lead to the can of Y1. Measure the resistance. With both terminators on the ends of the SCSI bus, you should measure between 12 and 20 Ohms. Is the resistance less than 12 ohms? No There is nothing apparent that will blow the SCSI fuse. However, if the resistance is higher than 20 ohms, then one of the terminators from one end of the bus is missing and should be added. A missing terminator will cause SCSI problems. Yes Trouble shoot the problem by disconnecting the cables, terminators, and devices hooked to the SCSI bus until you find what is causing the low ohm meter reading. Note: the resistance measurement will change when terminators are disconnected: with one disconnected the reading should be between 24 and 37 ohms; with both disconnected the reading should be greater than 1K ohms. Probable failures: * Extra terminators on bus (more than 2 total) * Shorted terminator, cable or improperly seated cable connector * Shorted SCSI device or device with internal terminator installed * If blowing intermittently, check connectors for seating and/or try flexing cable. Hot plugging SCSI cables will blow the fuse. SCSI fuse on SCSI adapter is known as part number at ce stock: the P/N IS 40F9736 ====================================================================== >(U)92101. Identifying the machine model via a script ----------- cut on dotted line for additional savings --------------- #|/bin/sh # # Little shell script to find machine type # UNIQ=`uname -m cut -c3-10` TYPE=`echo $UNIQ cut -c7-8` UNIQ=`echo $UNIQ cut -c1-6` STRING="You are the proud owner of a model " case $TYPE in "10") MODEL="530 or 730" ;; "11") MODEL="540" ;; "14") MODEL="540" ;; "18") MODEL="530H" ;; "1C") MODEL="550" ;; "20") MODEL="930" ;; "2E") MODEL="950 or 950E" ;; "30") MODEL="520" ;; "31") MODEL="320" ;; "35") MODEL="320H" ;; "37") MODEL="340" ;; "38") MODEL="350" ;; "41") MODEL="220" ;; "5C") MODEL="560" ;; *) MODEL="that has not yet been announced, please return it. " esac echo $STRING $MODEL. " The machine unique ID of "$UNIQ "is not the c" echo "machine's serial number." ------------------- cut here cut here -------------------------- Hope this helps, Tex ====================================================================== >(I)92102. NetWare/6000 + DOS 5 + other communications concurrently I've been using 9202 code for aix3.2 and NetWare/6000 with different DOS clients: attachment and file services worked fine with PS/2 8086 and 80386 and with DOS 3.30, DOS4.0 DOS 5.0 and Windows 3.0 with different type of shells (net3 net4 net5 netx bnetx) and with ODI drivers (lsl, lansup or token, ipxodi, netx or bnetxsequence) and with different frame types (TOKEN-RING or TOKEN-RING_SNAP) Everything worked fine and I could even install on a PC 8086 with 640k RAM, the following software sharing the Token Ring Adapter concurrently and simultaneously: . LAN Support Program v1.25 . IBM TCP/IP version 2.0.2 for DOS(access TCP/IP hosts) (using ASI interface) . IBM Personal Communications v2.0 for DOS (access VM) (using DXMT0MOD) . Netware Requester (access NEtware for AIX) (I had to generate ipx.com with WSGEN choosing LAN Support Program as Interface) I could recreate this configuration with DOS 3.3, DOS 4.0 and DOS 5.0. Of course with all three communication program loaded I had no more than 200k available for running other DOS applications but I could liberate some K's using QEMM386's OPTIMIZE utility. Ivan Montesino Martinez ====================================================================== >(U)92103. Potential security exposure with the mkgroup command The mkgroup command can be executed by everyone. This might be used together with NFS to tamper with file access. If you do not need the capability of allowing your users to create their own groups for the ease of file sharing the execute permissions of mkgroup should be turned off with the command "chmod o-rwx /bin/mkgroup". ====================================================================== >(U)92104. Free AppleTalk/EtherTalk Interface for the /6000 From the newsgroup comp.unix.aix: From wes.craigumich.edu Subject: netatalk-1.2 -> netatalk-1.2.1 Date: 17 Mar 92 06:12:36 GMT Organization: U of Michigan, Research Systems Unix Group netatalk is a kernel-level implementation of the AppleTalk Protocol Suite for BSD-derived systems. netatalk's primary services are routing, file service, print spooling, and outbound printing, in an AppleTalk networking environment. The current release contains support for EtherTalk Phase I. netatalk-1.2.1 runs on the following machines: MACHINE REQUIREMENTS ------- ------------ sun3*,sun4* sunos4.1 or greater, no source required dec mips ultrix4.1 and 4.2, no source required ibm rs/6000 aix3.1, no source required ibm pc/rt aos4.3, source required BSD vax 4.3BSD Reno, source required, likely to be portable to other machines running reno ... list of changes from pervious version omitted ... netatalk-1.2.1 is available via anonymous ftp from terminator.cc.umich.edu, in ftp/unix/netatalk/netatalk-1.2.1.tar.Z. A patch from version 1.2 to version 1.2.1 is also available. We have set up a mailing list to announce new releases and to answer general questions: netatalk-adminsitd.umich.edu. To join the list, send mail to netatalk-admins-requestitd.umich.edu. Research Systems Unix Group The University of Michigan netatalkitd.umich.edu c/o Wesley Craig +1-313-764-2278 535 W. William St. Ann Arbor, Michigan 48103-4943 ====================================================================== >(U)92105. chfs in AIX 3.2 allows to increment the filesystem size Prior to AIX 3.2 one had to use an absolute size when increasing filesystems with chfs. Now one can use an increment like in chfs -asize=+2000 /home This will increase the /home filesystem by 1MB. ====================================================================== >(U)92106. CERT Advisory - AIX uucp Vulnerability CA-92:06 CERT Advisory March 19, 1992 AIX uucp Vulnerability - - --------------------------------------------------------------------------- The Computer Emergency Response Team/Coordination Center (CERT/CC) has received information concerning a vulnerability with the UUCP software in versions of AIX up to 2007. The vulnerability does not exist in AIX 3.2. IBM is aware of this problem, and a fix is available as apar number "ix18516". This patch is available for all AIX releases from GOLD to 2006. The fix is in the 2007 update and 3.2 release of AIX. IBM customers may call IBM Support (800-237-5511) and ask that the fix be shipped to them. Patches may be obtained outside the U.S. by contacting your local IBM representative. - - --------------------------------------------------------------------------- I. Description Previous versions, except AIX 3.2, of the UUCP software contained incorrectly configured versions of various files. II. Impact Local users can execute unauthorized commands and gain unauthorized root access. III. Solution - If allowing users access to the uucp isn't necessary, disable it. % chmod 0100 /usr/bin/uucp - Obtain the fix from IBM Support. - Install the fix following the instructions in the README file. - - --------------------------------------------------------------------------- The CERT/CC would like to thank Steve Knodle, Clarkson University, for bringing this security vulnerability to our attention. - - --------------------------------------------------------------------------- If you believe that your system has been compromised, contact CERT/CC or your representative in FIRST (Forum of Incident Response and Security Teams). Internet E-mail: certcert.sei.cmu.edu Telephone: 412-268-7090 (24-hour hotline) CERT/CC personnel answer 7:30 a.m.-6:00 p.m. EST(GMT-5)/EDT(GMT-4), on call for emergencies during other hours. Computer Emergency Response Team/Coordination Center (CERT/CC) Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Past advisories, information about FIRST representatives, and other information related to computer security are available for anonymous ftp from cert.sei.cmu.edu (192.88.209.5). ====================================================================== >(U)92107. A substitute for the missing xmkmf on AIX 3.1 From the newsgroup comp.unix.aix: From davidwvista.atmos.uiuc.edu (David Wojtowicz) Newsgroups: comp.unix.aix Subject: Re: problems with imake Date: 20 Mar 92 15:26:20 GMT Organization: Atmos Sci at the Univ of Illinois at Urbana-Champaign Imake on AIX: the FAQ that just won't go away.... :-) Look in /usr/lpp/X11/Xamples. There's a readme file there telling you how to build all the stuff in that directory which includes imake under util/imake. Of course, for there to be anything in /usr/lpp/X11/Xamples you will have had to installed the "X11dev.src" image. Also, make sure you have enough space in your /usr file system if you build it all in place. Actually, its a bit of work to build it elsewhere as there are some hardwired paths in various places. As for xmkmf, there isn't any. Try this script instead: I call it ymkmf on our system to distinguish it from the real xmkmf that came with MIT X11R5 when we installed it. ------CUT HERE------- #|/bin/sh # xmkmf substitute for AIX3.1 if -f Makefile then mv Makefile Makefile.bak fi /usr/lpp/X11/Xamples/util/imake/imake -s -I/usr/lpp/X11/Xamples/util/imake.includes -TImake.tmpl -DTOPDIR=. >Makefile ------END------------- ====================================================================== >(I)92108. AIXTIPS NEWS now available on DIAL IBM in GERMANY AIXTIPS NEWS is now available in the NEWS section of DIAL IBM in Germany. As it is not possible for us to put them in other countries DIAL we make the unclassified part that we put on DIAL (it is also posted to comp.unix.aix) available on our TOOLS disk. Get it with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOG SUB AIXTIPS CUSTNEWS or use one of the shadows. ====================================================================== >(U)92109. HOTW: Shortcuts to often used paths in the Korn shell The Korn shell, (like the C-shell) understands a CDPATH variable. This shell variable will be used if you type in "cd somepath" and somepath is not directly resolvable. The cd command then checks the contents of $CDPATH and will try to resolve it with the directories listed in there. Lets assume the following line in your .profile: export CDPATH="$HOME:/usr:/usr/local" If your current directory is /etc, then typing "cd bin" will result in attempts to cd to /etc/bin, this will fail. Then cd will try to go to $HOME/bin. If you have a bin directory in your home directory, then cd will got there. Else it will end up in /usr/bin. If there were no /usr/bin, it would then try /usr/local/bin before giving up. afx ====================================================================== ====================================================================== >From the new jargon file: Big Room, the: n. The extremely large room with the blue ceiling and intensely bright light (during the day) or black ceiling with lots of tiny night-lights (during the night) found outside all computer installations. "He can't come to the phone right now, he's somewhere out in the Big Room." >92.04.6 Table of contents: (I)92110. MAR 25 FTN "AIX TCP/IP NETWORK MANAGEMENT" AVAILABLE ON TOOLS DISK| (I)92111. CLIENT/SERVER COMPUTING: THE NEW MODEL FOR BUSINESS ON MKTTOOLS (I)92112. Interleaf 5 with AIX 3.2 (U)92113. SECURITY PROBLEM WITH AIX 3.2 AND AIX 3.1.5 WITH PTF 2007 (I)92114. AIX CASE TTT Class in LaHulpe (U)92115. AIX SOFTWARE VENDOR OPPORTUNITY WITH AIX/ESA: (U)92116. AFS training from transarc (I)92117. There are some CATIA Answers waiting for you (I)92118. AIX 3.2 NLS Redbook internal review draft (I)92119. ANNOUNCING AIX/ESA: NATIVE UNIX ON S/390 PROCESSORS (U)92120. New FTP Server from IBM Europe (I)92121. IBM AIX CASE SOFTWARE DEVELOPMENT - QUICK REFERENCE GUIDE (I)92122. NetWare for AIX T3 material (U)92123. Warning: Don't use 3.2 boot diskettes with 3.1 machines (U)92124. IBM 2456 Image scanner support (I)92125. InfoExplorer License Extension for IBMers (I)92126. X11 NLS Q&A (U)92127. Printing a separator page with banner (I)92128. XGA adapter support prpq for the /6000 ............ (I)92129. DETERMINE IF AIX V3.2 IS ACTUALLY THE GA/GOLD LEVEL CODE. (U)92130. SONY WORM WDC-610 on a RS6000 (U)92131. Booting off of a Cybernetics(sp) tape drive (U)92132. X11.5 xterm problmes (U)92133. HOTW: Enabeling automatic reboot after crash on a /6000 ====================================================================== >(I)92110. MAR 25 FTN "AIX TCP/IP NETWORK MANAGEMENT" AVAILABLE ON TOOLS DISK| This presentation will give a detailed introduction to IBM's recently announced NetView/6000 product which manages a TCP/IP SNMP environment. Information to be covered will include a functional description of the capability to provide TCP/IP SNMP network fault, configuration, and performance activity. This FTN is scheduled for broadcast in the clear and at IBM locations on Wednesday, March 25, 1992 beginning at 11:30 am Eastern Standard Time. Copies of the handout will be available at IBM locations. In addition, a LIST3820 version will be available from the Tools Disk and can be received by issuing the following command: TOOLS SENDTO DALVM41B TOOLS AIXIC GET FTN92065 PACKAGE Any inquiries concerning this broadcast or the handouts may be directed to the sponsor, Karen Rodriguez at 8-421-5541 or DALVM41B(RODRIGUE). ====================================================================== >(I)92111. CLIENT/SERVER COMPUTING: THE NEW MODEL FOR BUSINESS ON MKTTOOLS This 4-page document meant for distribution to customers describes the positive business impact of implementing client/server systems at 5 different companies. The companies range in size from small to large; the applications are varied; and the systems implemented are different, with the PS/2, RISC System/6000, AS/400, and mainframe as focal points in different situations. One of the situations is multivendor. The document concludes with a summary of the advantages of working with IBM when implementing client/server computing. The document is on Market Tools in LIST3820 format as CSBUS PACKAGE. Retrieve with: TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET CSBUS PACKAGE Contact: Micks Purnell, Client/Server Marketing, White Plains NY 8-351-3279/RHQVM04(MICKS) ====================================================================== >(I)92112. Interleaf 5 with AIX 3.2 During CeBIT I installed the new Interleaf 5.3 on a RISC/6000 model 560 with AIX 3.2. During 2 hours late-evening tests I could not find anything that didn't work the same way it worked in Interleaf 5.2 under AIX 3.1.5. But some things (e.g. editing tables that were spread over several pages and linewidths greater than 1 point) were displayed much faster than in the older version. Load time has been very high (about 1-2 minutes) with Interleaf 5.2. Now you can use the "-fast" option when starting Interleaf with load time less than one minute. For those who cannot start with AIX 3.2 from scratch, I recommend to try the following: install only X11.rte within your AIX 3.1.5. Next we will do is testing with a model 220 - I hope that performance is comparable to the model 320. Freundliche Gruesse / Best regards Thomas Haemmerling ====================================================================== >(U)92113. SECURITY PROBLEM WITH AIX 3.2 AND AIX 3.1.5 WITH PTF 2007 All users of AIX 3.2 and those users of AIX 3.1.5 with PTF 2007 installed have a security exposure, however a fix is available. The passwd command on these systems will allow users access to unauthorized files. IBM has available a permanent fix for this problem. Until users apply this fix it is recommended that permission on the passwd command be changed by issuing the following command from the user with root authority. This will temporarily restrict password updating to the root user until application of the permanent fix: chmod 500 /bin/passwd As the permanent solution, users running the affected levels should order the PTF for APAR IX23505. This fix may be ordered from the local Support Center. Future shipments of AIX 3.1.5 Updates and AIX 3.2 will incorporate the fix to this problem. ====================================================================== >(I)92114. AIX CASE TTT Class in LaHulpe COURSE ANNOUNCEMENT Course name : AIX CASE stage 2 TTT (Teach the Teacher) Course code : AEU-3ACT202 Dates : April 27 - 30 (4 days) Class Manager : J. Simons (SIMONS at BRUVMIS1) Class Secretary : C. Monjoie (MONJOIE at BRUVMIS1) ================================================================ The course will be available in EEDU on March 23 ================================================================ TITLE: AIX CASE stage 2 TTT (Teach the Teacher) course (4 days) CODE: AEU-3ACT202 (La Gaude code: ACTTT922) AUDIENCE AIX and/or CASE (including AD/Cycle) specialized System Engineers, Countries' Technical Education Instructors. PREREQUISITES CASE knowledge. AIX using experience. Presentation or teaching skills. OBJECTIVE Provide audience with updated and/or advanced knowledge of AIX CASE products, and with supporting materials, in order to * SEs: be able to present and/or show demonstrations to other/new SEs and customers. * Instructors: get all needed info to develop Country-level modules or courses. CONTENTS * IBM AIX CASE strategy in depth * AIX CASE - AD/Cycle interoperability and positioning in large enterprise environments * Technical overviews of AIX CASE products (SDE WorkBench and Integrator, CMVC client and server, Library connector, C++ Compiler) * Demos and free hands-on activities * Vendor products integration status * Future product directions DATE & LOCATION * April 27-30 in La Hulpe (Belgium) ====================================================================== >(U)92115. AIX SOFTWARE VENDOR OPPORTUNITY WITH AIX/ESA: Today's announcement of AIX/ESA, with planned availability for June 1992, offers significant opportunity for current AIX Software Vendors. The IBM Software Vendor Systems Center will be offering an Early Test Program (ETP) for AIX/ESA Version 2 Release 1. This offering will allow vendors to remotely test their applications with AIX/ESA before it is generally available. The ETP will be available from March 1992, through September 1992. All software vendors are eligible to enroll in this program. Technical support and documentation will be provided to program participants. Software vendors with products that run on AIX can inquire about early access to IBM software products (current Early Test Programs), request to be placed on the AIX mailing list, or obtain assistance by calling 1-800-553-1623 or by writing to: IBM Corporation ATTN: ETP Advocate Software Vendor Systems Center 9 Village Circle Roanoke, Texas 76262 ====================================================================== >(U)92116. AFS training from transarc Note: As AFS is part of the upcoming DCE, this might be a good chance to get some initial education.... This is not meant as an ad for transarc.... Thanks to Uwe for the pointer. afx Date: Wed, 1 Apr 1992 07:57:13 -0500 (EST) From: Elaine_Wolfetransarc.com Subject: Sys Adm Training in Europe **TRAINING ANNOUNCEMENT** The AFS international community has grown tremendously over the past year --- approximately 40 sites representing fifteen different countries. As a sign of our commitment to supporting this global AFS community, Transarc is pleased to announce the first two AFS System Administrator classes in Europe. The classes are scheduled as follows: - June 24 through June 26, Boeblingen, Germany - June 29 through July 1, Bristol, United Kingdom The cost for the three-day class is $1,500 for educational sites and $1,700 for commercial sites (US dollars). Both classes will be held at Hewlett-Packard facilities. Upon registration, further information will be sent concerning exact location and local arrangements. Classes are limited in size and are reserved on a first come, first serve basis. The class is a full three days of lecture, and question and answer periods, generally from 8:30 until 5:00 each day. Prerequisites for the course are familiarity with UNIX system administration and a user-level knowledge of AFS. It is also helpful if you have had experience installing an AFS file server or an AFS cell. Topics covered include: - Overview of AFS commands - Managing client machines - Managing file servers - File server processes - Volume operations - System administration tasks To register for the class, you may complete the registration form that follows this message and return by either (1) e-mail, (2) FAX (01 412 338 4404), or (3) by physical mail to your AFS sales representative. If you have questions or would like further information, feel free to phone me at 01 412 338 4448 or e-mail to elaine@transarc.com. Sincerely, Elaine M. Wolfe Marketing Services Note: Primary site contacts at each of our AFS european sites will be receiving this message with a copy of the registration form through physical mail. ====================================================================== >(I)92117. There are some CATIA Answers waiting for you There is a new CATIA ANSWERS file on IBMUNIX. CATIA ANSWERS created (and is publicly appendable) by SCOTT at DFWVM04. Common Q's & A's about IBM's CATIA CAD/CAM product ====================================================================== >(I)92118. AIX 3.2 NLS Redbook internal review draft I have created NLSV32 PACKAGE on the AIXTOOLS disk. This is a draft of the soon-to-be-released Redbook. Many thanks to Anne Serre, Tim Hayashi and Antonio Freitas for their work in preparing this material. Also, many thanks to those of you who took the time to review earlier drafts and provide us with valuable feedback and direction. Naturally, we welcome and further feedback and corrections. In fact, part of the package is a README which describes ways in which we would welcome such feedback. I hope you find this book useful. Remember, however, that this is still an IBM Internal Use Only draft, as we have not yet completed the formal review process. Regards, Paul Lugo note: If you have NLS questions, read it, it explains a lot. afx ====================================================================== >(I)92119. ANNOUNCING AIX/ESA: NATIVE UNIX ON S/390 PROCESSORS Today, IBM announced a new, AIX/ESA* operating system built upon the Open Software Foundation's OSF/1** operating system with additional IBM enhancements to exploit large processor capabilities. AIX/ESA provides native UNIX** capability on the System/390* family of ESA-capable processors. AIX/ESA can also operate in a logical partition using PR/SM*, or as a guest of VM/XA* SP2.1 or VM/ESA*. AIX/ESA can be the ideal solution for a variety of server requirements. It can be used as a data server for general purpose computing. It makes a powerful compute server, addressing the number-crunching requirements of scientific, engineering, and technical users. Or it can be utilized as an interactive server for supporting a large number of terminal users. Planned Availability Date: Staged support beginning June 26, 1992 Detailed performance and staging information is available in the COMP database in HONE. The following deliverables will be available no later than April 15: Title Location Name/Number ----- -------- ----------- AIX/ESA Marketing Guide HONE COMP AIX/ESA Presentation Guide MKTTOOLS AIXP PACKAGE AIX/ESA Fact Sheet MKTTOOLS AIXFACTS PACKAGE AIX/ESA Proposal Material HONE PROP AIX/ESA Overview (Redbook) MECHANICSBURG GG24-3849 To request a package from MKTTOOLS, enter the following at the profs command line: TOOLCAT MKTTOOLS GET pkgname PACKAGE For additional details, see ivory letters 292-182 and 292-183 dated 3/31/92 or contact: Virginia Erikson Tl 351-2477 or 914-288-2477 RHQVM09(ERIKSON) John Keyes Tl 351-2478 or 914-288-2478 RHQVM09(JMKEYES) * Trademark or registered trademark of IBM Corporation. ** UNIX is a registered trademark of UNIX System Laboratories, Inc. ** OSF/1 is a trademark of the Open Software Foundation. ------- Seen on a T-shirt at SHARE Europe 92: AIX/ESA, building the better dinosaurs :-) afx ====================================================================== >(U)92120. New FTP Server from IBM Europe IBM Europe (Scientific & Technical Solutions) has set up a Public Domain Code Repository, containing code for AIX, on the European side of Internet. The name of this ftp-server is ftp.ctp.se.ibm.com (initial IP address is 192.36.23.44 but this is likely to change over time). For those running AFS you can reach the same files by cd to /afs/ctp.se.ibm.com/users/ftp. The primary focus is on software that runs under AIX3 on the RISC System/6000, but there will also be SW for AIX/ESA and AIX/PS2. We will also put other information of interest on this server. Over time we will develop this server to become the preferred source of Public Domain Software and related information in Europe, for IBMs AIX-platforms. If you have any SW to submit, or if you have comments regarding the ftp service, please contact myself or the administrator of this server Hakan Torbjar (torbjar at utc.chalmers.se). ====================================================================== >(I)92121. IBM AIX CASE SOFTWARE DEVELOPMENT - QUICK REFERENCE GUIDE A 25 page quick reference to AIX CASE was prepared by Greg Porpora, an AIX CASE Overlay Representative. It has just been placed on MKTTOOLS for field use. Its contents are as follows: Product Information Ported Vendor Tools by Life Cycle Element Requirements Analysis Analysis and Design Prototyping/Simulation Code Generation Test/Maintenance Configuration Management/Version Control Documentation/Publishing Editors Project Management Re-, Reverse Engineering AIX CASE DEVELOPMENT - C AIX CASE DEVELOPMENT - C + + AIX CASE DEVELOPMENT - FORTRAN AIX CASE DEVELOPMENT - PASCAL AIX CASE DEVELOPMENT - Ada AIX CASE DEVELOPMENT - COBOL AIX CASE DEVELOPMENT - DataBases AIX CASE DEVELOPMENT - Graphic Development AIX CASE DEVELOPMENT - 4GL AIX CASE DEVELOPMENT - OLTP AIX CASE DEVELOPMENT - GUI AIX CASE DEVELOPMENT - Object Oriented AIX CASE DEVELOPMENT - Framework Software Development Environment (SDE) Framework IBM Configuration/Version Control (CM/VC) SCLM/MVS Gateway Tool Integrator (Encapsulator) Embedded Development Environments RISC System/6000 : Present C + + Embedded Development Environment RISC System/6000 : Present FORTRAN/Pascal Embedded Development Environ. RISC System/6000 : Present C Embedded Development Environment RISC System/6000 : Present Ada Embedded Development Environment To get the guide type in the following from your OV/VM command line: TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET CSAIXCSE PACKAGE or TOOLCAT MKTTOOLS GET CSAIXCSE PACKAGE For more information contact: Jon Thew, Client/Server Marketing TL 351-3362, JONTHEW RHQVM04 ====================================================================== >(I)92122. NetWare for AIX T3 material I have placed the NetWare for AIX T3 Class Material onto the AIXTOOLS disk. You are free to take and use this material as you feel is appropriate. The package is still not 100% complete. I have more LIST3820's to add and I also ewant to add the Interleaf pictures. Mark Johnson ====================================================================== >(U)92123. Warning: Don't use 3.2 boot diskettes with 3.1 machines hallo, this is a tip from a bad experience, which I made: I used AIX 3.2 boot diskettes to boot up an AIX 3.1 machine, went into maintenance mode and tried to access hdisk0. After normal boot the machine halted with 553. It showed up, that the above test with 3.2 diskettes had deleted the the programs /etc/mount and /etc/umount. After restoring those programs the machine came up fine. Besides: It could be added to tip 92039 that another reason for 553 could be that /etc/mount is missing or not executable. Mit freundlichen Gr}~en D. Kunstmann ====================================================================== >(U)92124. IBM 2456 Image scanner support I.C.E. ANNOUNCES IBM AS/400 MODEL 2456 IMAGE SCANNER SUPPORT FOR THE IBM RISC SYSTEM/6000 Herndon, Virginia, March 16, 1992 - Integrated Computer Equipment (I.C.E.), an international developer of software products for the IBM RISC System/6000, announces a new product for the IBM RISC System/6000. Integrated Computer Equipment has now added support of the IBM Model 2456 Scanner to its IceScan/IceScan Plus products. IceScan is a combination of device driver and developer's toolkit for connecting SCSI scanners to the RISC System/6000. The IceScan software package speeds the integration of imaging and OCR applications requiring scanners by providing the device driver, configuration methods, ODM database entries, SMIT (System Management Integration [sic] Tool) interface and over 100 different image manipulation tools. IceScan Plus adds MOTIF Graphic User Interface (GUI) to IceScan. This software package supports both command line and AIX-windows. IceScan is designed for use by software developers wishing to build applications on top of it, it can also be used "Out of the Box" to scan documents, save images in a variety of popular formats and perform image manipulation and conversion from the command line. These new scanning products allow direct SCSI connection of the IBM 2456 Image Scanner to the IBM RISC System/6000. The IBM 2456 Image Scanner was originally an IBM AS/400 and PS/2 product which, by virtue of the IceScan/IceScan Plus products, will now operate with the RISC System/6000 computer systems. Integrated Computer Equipment 201 Elden Street, Suite 204 Herndon, Virginia 22070 Phone (703) 478-9478 FAX (703) 478-3361 Contact: J.P. LeGory, VP of Marketing ====================================================================== >(I)92125. InfoExplorer License Extension for IBMers If you're building a standalone InfoExplorer hypertext database for an LPP that runs on AIX, here's some useful information. Normally, customers need to buy an InfoExplorer License Extension ($150) to read databases produced by InfoCrafter. This is not true for databases produced by IBMers. All you need to do is get a copy of the cpyrt.dat file from Dan Lassig in Palo Alto. You need to include cpyrt.dat when you use InfoCrafter to build your databases. NOTE: if vendors are producing your documentation, do NOT give them the cpyrt.dat file. This means that *you* will need to do the builds, not the vendor. You do not need to (nor can you) bundle the License Extension with your LPP. Your LPP does not pay a royalty to KnowledgeSet. If you have questions, pleae contact Sheila McCallum in Austin. Laurie Lamar .......... 8-263-5682 ............ ====================================================================== >(I)92126. X11 NLS Q&A The following is a set of questions and answers which I received from IBM Iceland for which I got answers from Development. I think this is very useful information, so I am posting it here. Also note that Development is pretty close to getting X11R5 running and to a state that they can support beta. They are interested in knowing of anyone who is interested in being an X11R5 beta test site for the I18N support. Paul Lugo ITSC Austin ========================================================= Note that there are two types of problems: usage of new functions and interoperability problems (AIX versions): Client Server 3.2 3.2 - will be described below 3.2 3.1 - dead keys will not work 3.1 3.2 - will not be able to cut & paste in some locales Questions: ---------- 1) Keyboard and code page a. Are your systems delivered with a std. Icelandic keyboard (i.e., are all Icelandic special characters located on correct keys on the keyboard ? Ans: The keyboard support is divided into 3 parts in the X environment. a. /usr/lpp/X11/defaults/xmodmap/%L/keyboard - xmodmap b. /usr/lib/nls/loc/%L.im - input method c. /usr/lib/nls/loc/%L.imkeymap - IM keymap All of the xmodmaps are shipped with the X11rte. The %L.im and %L.imkeymap are shipped with the base OS but is packaged as an optional OPP under the bsl%L packages. The user needs to install the bsl to get b. and c.. Since X is running on a distributed network, all of the imkeymaps assume that they are running on a physical keyboard that corresponds to the territory of the locale. So substitute Is_IS for %L to find your keyboard files. b. Are special characters (brace, backslash, pipe symbol etc.) easily accessed/marked on the keyboard. Ans: Yes c. Are the engravings on the keyboard/location of keys according to Icelandic standards ? Ans: yes d. Are your systems delivered with ISO8859-1 fonts ? Ans: The X11rte when install provides a set of ISO8859-1 fonts. These are usually named *.iso1.snf.Z. We also provide the ISO8859-2,3,4,5,7 and 9 fonts as the X11fnt packages. and do your X-programs which are delivered with the system use these fonts ? Ans: Which font is used depends on which locale is used in the system. AIX 3.2 supports both PC Code (IBM-850) and ISO Codes (ISO8859-1). If Iceland is chosen as the primary language, at install time, the system is initially configured to an IBM-850 based locale (Is_IS). Once installed there is an option to switch the system to the ISO8859-1 locale (is_IS). Refer to the Upgrade Guide. Is the system when delivered setup to use these fonts ? Ans: Yes. In AIX 3.2 you may choose to have your system pre-installed and we will then deliver the system with ISO8859-1 or CP850 fonts. Other fonts will be shipped to you on tape, i.e. oldXfonts, MITXfonts, CP850, other ISO8859.2/3/4/5/6/7/8/9 fonts, Kanji etc. 2) National Language support a. Are X programs (aixterm, xterm, window system) delivered with your system enabled for 8-bit characters and dead-key support ? Ans: Yes b. Are X programs (Informix, Oracle, WordPerfect, Wingz etc.) which are delivered as executables able to run under X 8-bit enabled and can they use the dead key support in your X environment? I.e. can you configure your operating system and X to allow these programs to function correctly (dead key and 8-bit)? Ans: Depends on how these programs are internationalized. If they use the Motif toolkit AND call setlocale, they should provide the correct behavior. This would be a well behaved program. If they did their own keyboard mapping and drawing, then you need to talk to them. This is a bad behaving program since it can't support new languages the system would add later. How do you suggest we get Icelandic or dead-keys to be supported for these products ? Ans: If they are using Motif, they will need to call setlocale() before anything else. Otherwise, they should use Motif. If they can't use Motif, then they will need to wait for the X11R5 release. Do we need to negotiate with each SW vendor ? Ans: Yes, these vendors need to learn how to make their applications internationalized. The NLS Architecture group can help. c. Are programs delivered with source (like xedit) customizable to support dead keys ? Ans: Yes, but how easily depends on various issues. I believe that Motif based applications are ready to be customized for a given language, if setlocale is called. A non-Motif application like xedit, would need to call setlocale() and use the AIX Input Method interface in order to provide the correct keyboard input processing. I recommend that you use Motif for most of the basic IO to facilitate this work. Try xmeditor from the samples. Put a setlocale() in the main() before the call to XtToolkitInitialize() and watch it fly. Refer to /usr/include/X11/aix_keysym.h for a definition of the dead keys recognized by AIX 3.2 clients. I recommend that programmers don't code directly to these keysyms, but rather use the AIX Input Method or future X Input Method interface. d. If Motif is delivered with your system, are there any conflicts with the layout of the national language keyboard and the use of Motif functions as described in motif manuals? I.e. are there conflicts between the motif standard and your keyboard layout ? Ans: None that we are aware of. As you may know the user may re-define the keys. Currently, the Japanese Input Method does have a conflict with the ESC key when it is used with various commands, e.g. vi. 3) Future development a. If the answer to any of the above is negative could you please specify whether and when your company intends to rectify the problem? Ans: At this time AIX 3.2 provides the most advance NLS support known. Getting all of the information is the biggest problem today. I hope this helps. b. Do you monitor how the development of X11 is going with regard to national language support and how it will affect the Icelandic market? Ans: As already told. All of the support in X11 for languages like Icelandic is already there with AIX 3.2. How will X11R5 affect current X11 programs that may have been modified to work with Icelandic characters and dead-keys ? Ans: X11R5 is upward compatible. So if your program works on AIX 3.2, it will work when X11R5 is integrated. c. Are all of the above problems solved/solvable with X11R5 ? Ans: No. The real problem is that programs need to USE the NLS features in order to get the proper behavior. The current AIX 3.2 includes some of the X11R5 Xlib functionality (e.g., Xmb* functions for drawing) and provides all the support that you will need. With the X11R5 there will be more primitives that can be used. Also, we have enabled the Motif environment to have NLS support that will be compatible with the future updates. The AIX 3.2 Motif is expected to be upward compatible with the Motif 1.2 in terms of NLS support. So, if you use Motif, you should be OK. You can use the Xlib, Xmb and XCreateFontSet() primitives already. d. Which parts of X11R5 NLS are used in our X11R4 implementation in AIX 3.2? Ans: The libX11.a includes support for the drawing - XFontSet and many of the Xmb draw functions.  The libXm.a has already integrated the X11R5 drawing functions and is using input methods via a low level interface. Yet, when Motif switches to X11R5 X input method interface, we expect no changes to applications. We like to think that we have the most important items already integrated. The XIM is important for any application that is using drawables with the libXm. Otherwise they are taken care of. ====================================================================== >(U)92127. Printing a separator page with banner Here is a way to print the "DELIVER TO" user name in large characters at the top of the header page using the banner command, with the usual header page information just below it. Modify this example to suit your needs. As root: AIX 3.1.x AIX 3.2 ---------------------------- --------------------------- cd /usr/lpd/pio/custom smit -C lsvirprt vi QueueName:QueueDeviceName (select the virtual printer) AIX 3.1.x and AIX 3.2 ----------------------------------------------------- Search for the line containing the string ":sh:" Replace the string: %Ide/pioburst %FH %Idb/H.ascii with the string (all on the same line): USR=`echo "$PIOTO" sed "s/.*$//"`; USR=`/usr/bin/banner "$USR"`; HDR=`%Ide/pioburst %FH %Idb/H.ascii`; echo "n$USRnn$HDR" (the character and everything after it do not change) Save the file AIX 3.1.x AIX 3.2 ---------------------------- --------------------------- chvirprt (select the virtual printer) The environment variable PIOTO used above is documented with the pioburst command. Other available environment variables are: PIOTITLE (print job title) PIOFROM (user who submitted the print job) To have banner output appear within the standard header page instead of at the top, divide the H.ascii file into two files: USR=... USR=... HDR1=...H1.ascii... HDR2=...H2.ascii... echo "$HDR1nn$USRnn$HDR2" Thanks to Gary Petersen note: There might be ASCII-EBCDIC sreewups: left square bracket right square bracket backslash ====================================================================== >(I)92128. XGA adapter support prpq for the /6000 ............ note: This is in the US. Check localy for your country. Many questions have been appended regarding support for the XGA adapter. I've answered them somewhat cryptically in the past. For those who are interested today on hone, the PRPQ providing this support was announced. Attached is an excerpt of the hone announcement Steve Bade Austin SABADE at AUSTIN REVDATE = 920323 RPQNO = P91070 RPQTITL = XGA PREREQ This is a Non-Standard, I-Listed PRPQ. SPECIFIED OPERATING ENVIRONMENT: Machine Requirements: This program is designed to execute on a RISC System/6000 7012 POWERstation/POWERserver configured with the XGA display adapter, one VGA/XGA display, keyboard and mouse. A minimum of 16MB Random Access Memory is required when considering total system memory requirements. Total system memory includes memory requirements for AIX Version 3.2 for RISC System/6000 and AIXwindows Environment/6000, as well as the PRPQ. Additionally, a minimum of 160MB fixed-disk storage and one megabyte of VRAM for the XGA adapter are required. There are some limitations for the AIX operating system if you only have 160MB fixed-disk storage. Refer to Programming Announcement Letter 292-003 for AIX Version 3.2 for RISC System/6000. Hardware Requirements:  0 XGA adapter with 1MB VRAM (RPQ # 8A0556) 0 One of the following displays: - IBM 8514 Mod 001 Color Display - IBM 8515 Mod 001 and 021 Color Displays - IBM 8507 Mod 001 Monochrome Display Programming Requirements: 0 IBM AIX Version 3.2 for RISC System/6000 (5756-030) 0 IBM AIXwindows Environment/6000 (5601-257) Version 1.2 Limitations: 0 VGA/XGA displays must have the capability to support 1024 x 768 resolution 0 AIXwindows XGA support is an 8-bit per pixel, 2-dimensional PseudoColor server, providing for up to 256 colors displayed. 0 AIXwindows Environment/6000 Graphics Library (GL), AIX Personal GraHIGS (5) or other 3-dimensional graphics systems are not supported 0 Only 1 adapter per system unit is supported Installation Requirements 0 Installation requires another device attached as the console Performance Considerations: Performance may be affected by the total system memory available, the amount of fixed-disk storage available and type/performance of disk drives. Performance may also be affected by the type and function of the applications selected and running at the same time. ====================================================================== >(I)92129. DETERMINE IF AIX V3.2 IS ACTUALLY THE GA/GOLD LEVEL CODE. abridged from SETI: There are many levels of the AIX V3.2 code floating around in Branch Offices, Area System Centers and even customer locations. Now that the AIX V3.2 code has reached General Availability it is important and necessary to purge all non-GA level code. The support centers will verify that the GA/GOLD level of code is installed on the failing system before support can be provided. This applies to defect and howto support. It is not reasonable or possible for the non-GA levels of code to be supported. To determine if a system is running the GOLD/GA level code you will need to issue a couple of commands and check for the correct response: BOS (bos.obj): 'what /usr/sbin/mkspot' 14 1.25 com/cmd/dwm/mkspot, cmddwm, bos320 9202320a 1/15/92 13:54:34 BOS UPDATE (PTF: U401864): 'what /usr/lpp/diagnostics/da/dasync head -2' 25 1.21.1.6 R2/cmd/diag/da/async/dasync.c, daasync, bos320, 9202320d 1/17/92 16:45:09 38 1.3.1.7 R2/cmd/diag/da/async/dasync_tu.c, daasync, bos320, 9202320d 1/17/92 16:46:23 ====================================================================== >(U)92130. SONY WORM WDC-610 on a RS6000 Newsgroups: comp.unix.aix Organization: JDS Sommer GmbH, Frankfurt am Main, Germany >Has anyone tried to connect a SONY Writable Disk Controller WDC-610-00A >on a RS/6000 Mod. 320H. >For me, at takes 35 minutes to reboot the system and I'm still >unable to communicate with the Controller with the 'diag' command. The Problem was the SONY Disk Controller. The Revision of the Eproms has had some failure with synchronous SCSI transfers. Sony gave me the newest version of the Firmware and all works ok now. Here are the types of the seven correct Firmware Eproms (the last letter is important): 1. DRALPL-W 2. DRSYPL-N 3. DRSYPM-N 4. DRSYPH-N 5. DRSIPH-D 6. DRSIPM-D 7. DRSIPL-D Name: Andreas Thiedecke Company: JDS Sommer GmbH Address: D-6000 Frankfurt am Main, Jahnstr. 49 (Germany) E-Mail: athjds.in.sub.org * Telephon: +49 69 593200 * FAX: +49 69 553089 ====================================================================== >(U)92131. Booting off of a Cybernetics(sp) tape drive Newsgroups: comp.unix.aix > From: brianis.UUCP (Brian J. Zimbelman) > Subject: Booting off of a Cybernetics(sp) tape drive > Date: 18 Mar 92 00:35:28 GMT > > Has anyone tried to boot a RS/6000 off of a non IBM tape drive, specifically > a cybernetics tape drive. I am trying to help a poor soul who purchased > a 520H w/o a IBM tape drive. We seem to get all kinds of tape drive errors > from diagnostics. I'm not sure that the diagnostics understands non-IBM > drives. I did some asking around to try and get a definitive answer about booting from 3rd party tape drives. The answer is that for all released machines there was no effort made in the IPL ROS (Read Only Storage) microcode to support 3rd party tape drives. Some apparently will work, but this will have to be determined experimentally. However, the newest level IPL ROS that supports network booting and the integrated SCSI and ethernet was written with generic tape support in mind. I spoke with the IPL ROS SCSI device driver developer and he said that all of the drives they tried worked. Sorry, I do not have a list of drives. The bottom line is the code was written with 3rd party drives in mind. This new IPL ROS (which is now 512K rather than the original 128K) will be in all model 220s and most 340s and 350s (and future boxes). It is not in 560s, 320Hs, etc. that are currently shipping. The first few 340s and 350s apparently will still have older IPL ROS. The new IPL ROS on the 340 and 350 will be anything identifed as version 1.0, level 0.04 or later. This can be examined by using diagnostics to look at the vital product data (VPD). Currently there is no plan to retrofit this new IPL ROS into existing machines as an EC. If this is a high priority item then I would suggest you make this known through your SE, branch office, or whomever you deal with on the marketing/service side. Contrary to some popular opinion we do listen to customer requirements. Unfortunately not all can be implemented so the more voices asking for the same thing the more likely it will be done. About the diagnostics errors, the diagnostics code runs through the AIX tape device driver, so there was no support for 3rd party tape drives prior to AIX 3.2. If you are getting the errors on a 3.2 system then I would look at the error log. If you are getting logged errors while running tape diagnostics then you can send in the sense data to IBM support for analysis. This should help with identifying why the drive and adapter and/or device driver are not getting along. - Fred My remarks and opinions are mine alone... ____________________________________________________________________________ Fred L. Johnson Internet: johnsonaixwiz.austin.ibm.com IBM Personal Systems Programming inet: johnsontanstaafl.austin.ibm.com AIX BOS Development vnet: FJOHNSON at AUSVMQ 11400 Burnet Road, 9540 phone: (512) 828-2682 Austin, TX 78758-3493 tie line: 678-2682 ___________________________________________________________________________ ====================================================================== >(U)92132. X11.5 xterm problmes >From fritzscipp.UCSC.EDU (Frederick Staats) Newsgroups: comp.unix.aix Organization: Santa Cruz Institute for Particle Physics Add this to the top of X11R5 mit/clients/xterm/main.c: #ifdef AIXV3 #define USE_SYSV_UTMP #define HAS_UTMP_UT_HOST #define WTMP_FILENAME "/var/adm/wtmp" #endif And your utmp problems should go away. If you want xterminal sessions to go into the wtmp file you need to define -DWTMP in the Imakefile and be sure the WTMP_FILENAME is set to the right place. (The above is correct for AIX 3.2.) The following program run in the background by root will clean up the utmp file (I can't remember who first posted it, it may be in the FAQ which hasn't been posted in a while... The above should go in the FAQ also.) To make: cc -o utmpd -O utmpd.c Program: #include #include #include main () int fd; struct utmp utmp; while (1) if ((fd = open ("/etc/utmp", O_RDWR)) < 0) exit (1); while (read (fd, &utmp, sizeof utmp) == sizeof utmp) if (utmp.ut_type == USER_PROCESS && kill (utmp.ut_pid, 0) |= 0) lseek (fd, - (long) sizeof utmp, 1); utmp.ut_type = DEAD_PROCESS; write (fd, &utmp, sizeof utmp); close (fd); sleep (60); -- Frederick Staats fritzscipp.UCSC.EDU -- (408) 459-3575 Santa Cruz Institute for Particle Physics University of California at Santa Cruz ====================================================================== >(U)92133. HOTW: Enabeling automatic reboot after crash on a /6000 Using chdev -l sys0 -a autorestart=true will enable your machine to reboot automatically after crashes. This will work only if the key is in the normal position. ====================================================================== ====================================================================== >From the new jargon file: Blue Glue: IBM n. IBM's SNA (Systems Network Architecture), an incredibly losing and bletcherous communications protocol widely favored at commercial shops that don't know any better. The official IBM definition is "that which binds blue boxes together." See fear and loathing. It may not be irrelevant that Blue Glue is the trade name of a 3M product that is commonly used to hold down the carpet squares to the removable panel floors common in dinosaur pens. A correspondent at U. Minn. reports that the CS department there has about 80 bottles of the stuff hanging about, so they often refer to any messy work to be done as `using the blue glue'. >92.04.22 Table of contents: (I)92134. Withdrawl of 8Bit Sabine (U)92135. No curses boxes in 3.2 (I)92136. Some basics about 3D Graphics (I)92137. New GTO whitepaper (U)92138. AIX V3 SNA LU0 support in AIX V3.1.5 and up. (I)92139. TCP/IP NEWSLETTER ANNOUNCED---TCP/IP CONNECTION (I)92140. PTFs for IBM RISC System/6000 Model 220 (I)92141. Caring for Your System Package (I)92142. UNIX WORKSTATION RELIABILITY AND CUSTOMER SATISFACTION REPORTS NOW (U)92143. RS/6000 VMEbus Serial Controller Board from SBE, Inc. (I)92144. NetWare Routing and other issues .... (I)92145. 100.3 SPECMARK PERFORMANCE IS BEST IN INDUSTRY (I)92146. RISC SYSTEM/6000 ELECTRONIC DELIVERABLES - NOW AVAILABLE ON MKTTOOLS (I)92147. PERFORMANCE DATA FOR NEW RISC SYSTEM/6000 POWERSERVER 970 (I)92148. National Language Version Of X3270 Beta version available (U)92149. PS/2 ITBU and '/etc/backup' inefficiency (I)92150. AADU 2.1, PC/3270 and Netware can coexist, can't they??? (U)92151. HOTW: Breaking/Wrapping Lines ====================================================================== >(I)92134. Withdrawl of 8Bit Sabine This is for the US. Other countries might choose a different date. HIGH-PERFORMANCE 8-BIT 3D COLOR GRAPHICS PROCESSOR (f/c 2780) SCHEDULED FOR WITHDRAWAL ON 4/21/92. The high-performance 8-bit 3D color graphics processor (f/c 2780) is being Withdrawn from Marketing on April 21, 1992. Previous announcement letters stated that orders for f/c 2780 would be accepted on an as-available basis until supplies were exhausted. Supplies have now been exhausted and orders for systems that include this feature will remain unscheduled. Reference announcement letters 191-196, 192-004, 192-005, or 192-006 for additional details. ====================================================================== >(U)92135. No curses boxes in 3.2 Because of the ISO codeset support some things in curses changed (actually terminfo). From /usr/lpp/bos/README: 9.Incompatibility between aixterm/hft-3.1 and aixterm/hft-3.2 Older versions of hft operate in codeset IBM-850 (pc850). This codeset has box characters used for drawing boxes around things for smit. The new codesets that are supported don't have these box characters. New escape sequences were added to the terminfo entry to support drawing these characters no matter what codeset is being used. The older versions of hft (for example using a AIX v3.1 hft and "tn" in to a AIX v3.2 machine) set the TERM environment variable to "hft-old" (or "hft-m-old"). These terminfo entries will assume the IBM-850 codeset. ====================================================================== >(I)92136. Some basics about 3D Graphics AIXTOOLS: Information: 3DGRAPH PACKAGE created by NINA at AUSVM8. "Draft of 3D Computer Graphics Concepts" Get it via TOOLCAT AIX ====================================================================== >(I)92137. New GTO whitepaper Get it with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET GTOWP SCRIPT or TOOLS SENDTO DALVM41B IBMPC AIXDOC GET GTOWP SCRIPT ====================================================================== >(U)92138. AIX V3 SNA LU0 support in AIX V3.1.5 and up. There are two different types of LU0 support available: 1. LU0 primary support. It is needed to support some special devices like IBM4680 and works o n l y on SDLC lines | 2. LU0 secundary support. This support is needed for HCF and NetView-DM catchers within AIX Network Management/6000 and works on a l l SNA connections, which are : SDLC and X.25 lines, Token Ring and Ethernet LANs| To use this support, the LU0 must be defined in the Generic LU Address Registration profile of AIX SNA services. In addition to this, the LU addresses used for LU0 must be configured using the 'lu0config' command. After definitions done, the lu0 secundary support must be started like 'lu0 -Sattachmentname -B &'. Other support for AIX Network Management/6000, AIX NetView Service Point or AIX NetView/6000 for sending Alerts to any Host Netview or receiving RUNCMDs is not done via the LU0 | This happens via the SSCP-PU session which is available every time a SNA host connection is activated and is also not limited to any specific type of physical connection. Examples how to define the LU0 support can be found in 'Communications Programming Concepts SC23-2206' and 'Experiences managing RS/6000 AIX using Netview, HCF and Netview-DM GG24-3606'. MfG, regards Harald Schneider ====================================================================== >(I)92139. TCP/IP NEWSLETTER ANNOUNCED---TCP/IP CONNECTION A New TCP/IP newsletter is now available on MKTTOOLS. The name is "TCPNEWS". This periodic letter will have short, concise articles about "What's new in TCP/IP". M&S Marketing and NS TCP/IP Development believe that 1992 will be a year of continued growth for TCP/IP and will present an opportunity to significantly increase market share for IBM's suite of TCP/IP products: MVS, VM, OS/2, DOS, OS/400, and AIX. The intent of The TCP/IP Connection is to keep you and your customers informed about what we're doing to help make that happen. So we hope you will read this newsletter and share what you've learned with your customers. We also hope that The TCP/IP Connection, which we plan to publish on a regular basis, will become a vehicle for sharing your successes and experiences in the dynamic and exciting area of TCP/IP. Since the newsletter will be published periodically we suggest that you SUBSCRIBE to the MKTTOOLS package so that you will automatically receive future issues. Prior issues will be left on MKTTOOLS and new issues will be added. If subscribe you will just receive the new issues as they are added. For more information contact: ALAN REINHOLD REINHOLDRALYDPD.VNET.IBM.COM 8/352-3173 ====================================================================== >(I)92140. PTFs for IBM RISC System/6000 Model 220 The following is a warning about PTFs necessary for operating IBM RISC System/6000 Model 220 in diskless, dataless, or standalone mode. Each customer receiving the PTFs should get a copy of a document called "NOTICE TO LICENSEES" along with the PTFS. I strongly recommend to read the "NOTICE TO LICENSEES" document carefully before starting the installation of any PTFs. If you don't have a copy of this document try to get one. Each branch should have access to it. This note is only a short abstract of the information contained in "NOTICE TO LICENSEES", and this note addresses only those who work with IBM RISC System/6000 Model 220 (diskless). The following PTFs have to be applied in that sequence (the sequence is important!!). 1. bos.obj U402346 prerequisites: U401977 2. bos.obj U402637 prerequisites: U401986 U402153 U402335 U402346 and U402637 are updates to installp and instlclient and must be installed first. If they show as "CANCELLED" repeat the APPLY process. 3. bos.obj U402206 diskless PTF, reboot after applying. prerequisites: U402023 U401962 U401963 U401968 U401970 U401972 U401977 U401980 U401986 U402027 U402043 U402093 U402202 U402190 U402346 U402335 U402632 U402635 U402637 U402640 U402664 4. bos.obj. U402109 Model 220, reboot after applying. prerequisites: U402659 U402666 U402643 U402641 U402639 U402417 U402416 U402415 U402414 U402413 U402454 U402411 U402409 U402408 U402407 U402406 U402405 U402404 U402402 U402401 U402400 U402330 U402093 5. bos.obj. U402833 fix for xlpp command 6. X11rte.obj U402376 AIXwindows, GT1 Visual support U402470 U402083 U402659 These PTFs have to be applied to the server as well as to the client code in a diskless environment. Read the /usr/lpp/bos/README.diskless file for more information. Regards, Peter Koepp ====================================================================== >(I)92141. Caring for Your System Package The ITSC has developed a document that reviews the topic of Systems Management for smaller AIX based RISC Systems. This document has been placed on a TOOLS disk for ease of access. Both LIST3820 and Bookmaster source have been placed in the tools based package. This document has been previously made available selectively and is titled "AIX Systems Management Tips" and the presentation made available at the La Hulpe Technical conference. See the CAREFYS ANNOUCE file for an overview of the package. It is anticipated that this document could be used in the following ways - Tailoring of the document with specific information for specific situations.(for example a large customer or business partner) - Inclusion of local information on support hotlines (SPOC) and other relevant local data to form a basic text on systems management for a specific geography. - Rework into a short class or presentation for discussion of this topic. Access to package using TOOLCAT (if you have a local copy of the AIXTOOLS CATALOG) or alternatively, use the following commands to access the PACKAGE on the Yorktown AIXTOOLS repository. To access just the ANNOUNCE file TOOLS SENDTO YKTVMV TOOLS AIXTOOLS GET CAREFYS ANNOUNCE To access just the entire PACKAGE TOOLS SENDTO YKTVMV TOOLS AIXTOOLS GET CAREFYS PACKAGE Mark Johnson - ITSC Austin MARKJOHN at AUSVM8 ====================================================================== >(I)92142. UNIX WORKSTATION RELIABILITY AND CUSTOMER SATISFACTION REPORTS NOW AVAILABLE ON COMP (use the fastpath COMP on HONE) These monthly reports are based on end user survey's conducted by Reliability Ratings, an independent survey company. Vendors included are IBM, DEC, SUN and others. As these survey's are expanded more vendors will be added. The statistics published are: o Reliability - Mean Time Before Failure (MTBF), System-level annual failure rate, CPU-level annual failure rate. o Customer Satisfaction Statistics - Reliability, Service, Performance, Functionality, Tech support, Graphics and Price. o Usage This month was the first month that included the RISC System/6000 model 320. Next month the RISC System/6000 500 series will be added. Caution: These reports are done by an independent survey company. IBM has not certified these reports. No indications should be given to customers that IBM is involve with the interpretation of the data. To access these reports type "RRR" on the SOURCE line of the COMP menu screen. Questions on this notice are to be forwarded to: RHQVM05(AARTALE) ====================================================================== >(U)92143. RS/6000 VMEbus Serial Controller Board from SBE, Inc. SBE, Inc. announced it's VCOM-24 board is now available for use with AIX o the RS/6000. The SBE VCOM-24 is a four port VME based serial controller board capable of handling data in speeds up to T1 (1.54 MB per second). Th four ports are independently protocol programmable and support variou interface requirements such as 232C, 422, 449, 530, V.35 and X.21/V.11. SBE has ported the X.25 packet switched network communications software to th VCOM-24 and now offers the ability to run the protocol on the controller boar instead of out of the host. The obvious advantages of off-loading the protocol handling activities, thereby eliminating the overhead to the cpu will generally result in an increased performance and overall throughput o the host computer. The SBE VCOM-24 product is supported by the Bit3 Computer Microchannel t VMEbus Adapter, Model 477-010. Future implementations include the availabilit of the VCOM-100 board for VME based FDDI communications. SBE, Inc. will b demonstrating the VCOM-24 board in the Bit3 Computer booth at the Technica Computing System's Executive Conference in Palm Springs, California, April 28-30. For more information contact Gil Williams, SBE Inc. at 817/261-2017 or FA 817/261-2207. ====================================================================== >(I)92144. NetWare Routing and other issues .... From the NETWARE FORUM on IBMUNIX: This note contains stuff on routing .... I would love to hear feedback on any successful implimentations of NW4AIX. First thing ... I have placed all the course notes on the AIXTOOLS disk TOOLS SENDTO YKTVMV TOOLS AIXTOOLS GET NW4AIXT3 PACKAGE It is still not fully finished ... but all the bookmaster source is there. In a previous note i made comments that there were some problems with routing. I have tested this and spoken to the Change team. There are some confusing items on the databases ... there is a PMR that says routing is not done and SETI items that says it does work. Routing does function. I have seen the two following configs work .... 1/ -A- PS/2 -B- -C- +------+ TR +------+ ______________ 6000 Native Ethernet NW- ----NW -4AIX Intel __ +------+ +------+ PS/2 A can see servers B and C and login or attach to either. 1/ -A- PS/2 -B- -C- +------+ E'net +------+ __________ 6000 Native TR NW- ----NW -4AIX Intel *802.3__ *Et-II *TR +------+ +------+ +------+ ---- M220 NW- -4AIX *Et-II *802.3 +------+ -D- * - LAN types configured. PS/2 A can see servers B, C and D and attach or login to all. The RISC System Model 220 used as server D uses only the onboard ethernet adapter. There are two major issues to note so far ..... 1/ I have not been able to bind two frame types to the same board. For example T-R and T-R_SNAP to the same TR board. I could if I had TWO T-R boards. In the case of server D while I had one Ethernet adapter I was using two different protocols ... /dev/et0 and /dev/en0 ..... at the board level .... hence the ability to bind Ethernet II and Ethernet 802.3 to the same board. 2/ I ran into alot of problems when I set up a router that replicated an existing router. For example, if I made router A between LANs 00009634 and 00005582, and I already had a router with knowledge of that route, then when I start the 6000 router ... other machines already have an entry in their routing table for that route ... you can flush these tables but RIP refills them with data from other servers ... we have abour 12 visible here at the moment hence the problem. You must ensure the route created implicitly by creation of the two or more networks are unique. OTHER Issues ..... - Mac support. There is no short term possibility of seeing Mac support in the current product. Novell may add the SPG gateway support to the next release of NetWare for UNIX V3.11 but this is not certain. I suggest that if you anticipate availability for Mac with NetWare for UNIX V3.2 then you are more likely to have your expectations met. Contact me if you have any specific question about product function. Mark Johnson Advisory Systems Engineer ====================================================================== >(I)92145. 100.3 SPECMARK PERFORMANCE IS BEST IN INDUSTRY April 21, 1992 IBM ANNOUNCES POWERFUL NEW RISC SYSTEM/6000 SERVER WITH ENHANCED CHIP, MICRO CHANNEL BUS TECHNOLOGIES; SUPPORT FOR GIGABYTE DISK DRIVES ALSO ANNOUNCED WHITE PLAINS, N.Y., April 21 . . . IBM today announced a new high-end, rack-mounted RISC System/6000* server that delivers double the expansion capability and nearly twice the disk storage capacity of IBM's existing high-end server model, while establishing a new standard for performance# in the industry. The POWERserver 970 achieves a SPECmark** rating of 100.3, making IBM the first company to produce a RISC system that scores 100 or better on this popular industry benchmark. The 100.9 transactions-per-second performance on the Transaction Processing Performance Council Benchmark A (TPC-A**), is also the best result in the industry for a single-processor system. With the 970, IBM introduces new chip technology and major enhancements to the Micro Channel* input/output (I/O) bus used in the RISC System/6000 family. The combination of high performance and flexibility in the new model makes it ideal for customers such as banks and telephone companies, which have large, transaction-intensive requirements, as well as other users who need a powerful network file server, numeric intensive compute server or database server for their commercial applications. The 970 is based on IBM's Performance Optimization with Enhanced RISC (POWER) Architecture and uses IBM's AIX* Version 3.2 for RISC System/6000 (AIX/6000*) operating system with selected enhancements to support the new model. AIX/6000 Version 3.2, introduced in January 1992, is a robust, user-friendly implementation of the UNIX** operating system that provides higher performance and improved quality, systems management and installation capabilities compared with previous AIX/6000 releases. "The POWERserver 970 delivers the performance, expansion and competitive pricing that today's commercial customers need for their critical business applications," said IBM's Jeff Mason, Advanced Workstations and AIX Systems director. "We continue to deliver on our commitments to advance both the power and usability of our RISC hardware products and AIX/6000 operating system, making the RISC System/6000 family a leader in the open systems market." Planned availability of the POWERserver 970 is June 26. The system unit base price is $94,500, with a minimum entry configuration starting at $97,822. Conversion options will be offered to allow current users of POWERserver 930 and 950 systems to migrate to the higher performance of the 970 while protecting their existing investments in adapters, disk storage and other media devices. Standard features of the POWERserver 970 include 64 megabytes (MB) of memory, expandable to 512 MB, and 2.7 gigabytes (GB) of internal disk storage capacity, expandable to 20.5 GB, with up to 132.9 GB of total storage possible through the use of optional external expansion racks. The 132.9 GB of maximum storage is the most in the product line and nearly twice as much as can be supported on the POWERserver 950. Other standard features are an 8 millimeter tape drive, a 1.44 MB 3.5-inch diskette drive, a CD-ROM drive and an integrated Small Computer Systems Interface (SCSI) port. The new system supports the more than 6,000 leading AIX/6000 applications available for the RISC System/6000 family. A wide variety of connectivity and storage options can be used, including the IBM 9333 High-Performance Disk Drive Subsystem. In addition, IBM today announced three new disk drives that will be available for most of the workstations and servers in the RISC System/6000 product line, providing improved growth and flexibility. Two of the drives, a 1.0 GB 3.5-inch model and a 1.37 GB 5.25-inch model, support the SCSI standard and have a planned availability of April 24. The 1.0 GB drive incorporates IBM's industry-leading magnetoresistive head technology, which allows data to be read more accurately and quickly. Data stored on this type of drive can be packed more densely onto the disk surface. The third drive is a 1.07 GB 5.25-inch Serial-Link model with a planned availability of May 8. Serial-Link is IBM's innovative high-performance connection, which is used in the 9333 subsystem. The 9333 subsystem can be used with rack and deskside RISC System/6000 models and as of today can also be used on the POWERstation/POWERserver 340 and 350 desktop systems, increasing the maximum supported storage on these models from 8.8 GB to 30 GB. IBM also plans to make available ruggedized versions of the POWERstation/POWERserver 340 and 350 systems. Ruggedized systems are designed for harsh environments and can withstand a wider range of temperature, dust, humidity and vibration conditions. They are applicable for use in the field by researchers and geophysicists, on the plant floor by manufacturing firms, or rack-mounted in trucks or other vehicles. Price reductions of 17 percent on the POWERserver 950, which was the most powerful rack-mounted server in the family, and 14 percent on the 400 MB disk drive for the RISC System/6000 line were announced as well. A Wealth of New Technology The new IBM RISC System/6000 POWERserver 970 introduces several "firsts" for IBM's family of POWERstations and POWERservers. A new 0.5 micron Complementary Metal-Oxide Semiconductor (CMOS) process was used in the production of its 50 megahertz processor complex, which allows greater circuit density and a quadrupling of the amount of on-chip instruction cache memory to 32 kilobytes. This increase in the size of the cache -- a type of very fast memory that optimizes system throughput -- contributes to the enhanced performance of the 970. Because of a two-way set-associative cache design, RISC System/6000 processors are very efficient and able to achieve comparable or better performance results than other systems that have larger caches. IBM also introduced a number of enhancements to the Micro Channel I/O bus and the I/O controller used in the 970. These new features expand the power and flexibility of the Micro Channel Architecture and demonstrate IBM's commitment to protecting customers' investments by providing full downward compatibility with existing RISC System/6000 Micro Channel adapters. The 970 sets a new standard for RISC System/6000 bus performance by using a faster implementation of the Micro Channel I/O bus, called 64-bit Streaming Data mode, which increases the peak data transfer rate to 80 megabytes per second (MB/second) -- double the peak transfer rate of 40 MB/second available on existing models. The "sustained" data transfer rate of the 970 Micro Channel bus has been quadrupled to 72 MB/second -- up from the 18 MB/second rate achievable on the POWERserver 950.# This increase in the 970 bus performance allows applications to more quickly access data and improves overall system response time. A new extended I/O channel controller chip is used for the first time in the POWERserver 970 as well, providing a number of performance improvements that contribute to the overall speed and efficiency of the system, especially in I/O intensive environments. The chip, which acts as the interface between the processor and the Micro Channel bus, enables most existing RISC System/6000 Micro Channel adapters to achieve higher performance when used in the 970 even though they were not designed to fully exploit the 64-bit Streaming Data protocol. IBM's existing 40 MB/second SCSI controller, for example, achieves a "sustained" data transfer rate of 31 MB/second when used in the 970, as compared to the 15 MB/second rate it achieves on existing RISC System/6000 models. In addition, "peer-to-peer" transfer capability has been enhanced through the use of the extended I/O channel controller chip, permitting Micro Channel devices to directly access other Micro Channel devices without going through the processor. This function is especially beneficial for environments that support network routers, channel gateways and visualization applications, for example. The POWERserver 970 is also the first RISC System/6000 model to feature two Micro Channel buses. Each functions independently and is capable of operating at the 80 MB/second peak data transfer rate. This feature allows customers to add eight more expansion slots through an optional Micro Channel Expansion Board, for a total of 16 slots. This enables more peripheral devices to be added and provides support for a larger number of users. The Micro Channel Expansion Board can accommodate new Type 9 form factor (9-inch high) Micro Channel adapters. This is due to enhanced cooling and mechanical packaging techniques used in the 970 design, which make the system ideal for industrial environments where larger form factor cards are often required to support specialized devices. SystemXtra* Service Offering The IBM products announced today are eligible for SystemXtra for RISC System/6000, an optional support service designed specifically for the AIX/6000 environment. This total support solution provides a single point of contact for assistance and problem resolution, including unlimited access to IBM's support structure through a toll-free number that connects the user to a designated technical focal point familiar with that user's installation. Under SystemXtra, customers can also choose to have IBM arrange for installation of program updates and other maintenance activities. # # # * Indicates trademark or registered trademark of International Business Machines Corporation. ** Indicates trademark or registered trademark of respective organization: SPECmark (Standard Performance Evaluation Corporation); TPC-A (Transaction Processing Performance Council); UNIX (UNIX System Laboratories, Inc.) # Performance measurements are based on IBM testing of development-level systems. These values should be indicative of generally-available systems, but no warranties or guarantees are stated or implied by IBM. IBM recommends application-oriented testing for performance predications and offers results for commonly reported benchmarks as an initial indicator. SPECmark results represent the geometric mean of the 10 SPECmark tests and were completed using the AIX XL FORTRAN Compiler/6000 Version 2.2 and AIX XL C Compiler/6000 Version 1.2. TPC Benchmark A results are reported for performance (tpsA), and price/performance ($/tpsA), which represents the five-year cost of ownership -- hardware, terminals, software, maintenance -- divided by the tpsA. The POWERserver 970 achieved a $/tpsA result of $12,417. ====================================================================== >(I)92146. RISC SYSTEM/6000 ELECTRONIC DELIVERABLES - NOW AVAILABLE ON MKTTOOLS April 21, 1992 To support the April 21, 1992 RISC System/6000 announcement, the majority of the deliverables are available in electronic form on the marketing tools disk MKTTOOLS. Proposal Insert Package Name POWERstation/POWERserver 220 G2213278 POWERstation/POWERserver 300 series G2213279 POWERstation/POWERserver 500 series G2213223 POWERserver 950, 970 G2213123 RISC System/6000 Storage Devices G2213079 RISC System/6000 Facts & Features G3209878 To access the 220, 300, 500, 900 and Storage Devices proposal insert files, type the following command on your PROFS command line: TOOLCAT MKTTOOLS GET pkgname PACKAGE substituting the name of the package you want to access for "pkgname". The file will come to you as a LIST3820 file. You should print it on a 3820 printer, as you would any LIST3820 file. Each of these proposal inserts is 4 pages containing product features, benefits and a picture of the unit being described. G3209878 contains the latest RISC System/6000 product performance and configuration information. In addition, it contains entry station and server configurations and prices for each model. RISC System/6000 Facts & Features is a tersed LIST3820 file, due to its size. Access it using the TOOLCAT command described above. Then unpack it for printing by typing the following command at your PROFS command line: TERSE G3209878 TERS3820 A1 RS6KFF LIST3820 A1 (UNPACK Then, print RS6KFF as you would any LIST3820 file. Presentations The following presentations have been prepared to support the April 21 RISC System/6000 announcement. Title Package Name # of Files 4/21 Announcement Overview Presentation G3260193 3 RISC System/6000 Product Excellence G3209886 10 RS/6000 Product Excellence Changes RS6KPEUP 4 Each presentation package contains from 3 to 7 files of presentation charts in tersed LIST3820 format. These files end with a number in the 8th position of the name. They are tersed LIST3820 files containing from 8 to 10 presentation foil masters. In order to unpack them for printing, follow the unpacking instructions outlined above. Each package also contains a file with a name which ends with the letter p as the 8th character. This is the Encapsulated PostScript version of the presentation. If you have a PostScript printer and know it's procedure for printing Encapsulated PostScript files, download the file and print it on your PostScript printer. Otherwise, you may want to erase the file. The files in the package with c in the 8th position of the name are versions of the presentation in condensed 4-charts-to-a-page format. You may want to print this version of the presentation at full size. If the file type is TERS3820 , unpack it as outlined earlier, before you print it. Also, available in the Product Excellence packages arepresentation note files. These files have a t in the 8th position of the name. They should be printed as you would print a LIST3820 file. If you pulled the Product Excellence presentation for the January 21 announcements, you do not need to pull it again. Simply request package RS6KPEUP . You will receive two tersed LIST3820 files named CHANGES1 and CHANGES2--the foils in the presentation which were updated for the 4/21 announcement. Unterse these files, then print them as you would any LIST3820 file. Other Electronic Deliverables RISC System/6000 Marketing Guide The Marketing Guide is intended for use by reps, SE's and business partners. It contains product information key to selling the RISC System/6000, marketing pointers and competitive information. It has been updated for the 4/21 announcements. The package is named ZZ304014 . It is about 50 pages long. Access it using the TOOLCAT command. Unpack it using the TERSE command, then print it on a 3820 as you would a LIST3820file. RISC System/6000 Pocket Pricer The package file is Z3260227. This is a tersed LIST3820 file. First unpack it, then print the LIST3820 file. Deliverables in Mechanicsburg RISC System/6000 Executive Overview G520-6678-06 RISC System/6000 Facts & Features G320-9878-08 RISC System/6000 Reference Guide G326-0151-03 These brochures will be available for ordering from Mechanicsburg no later than 4/27/92. Questions on this notice are to be forwarded to: RHQVM08(MARTHAL) ====================================================================== >(I)92147. PERFORMANCE DATA FOR NEW RISC SYSTEM/6000 POWERSERVER 970 April 21, 1992 IBM Internal Use Only Performance and price/performance information for the IBM RISC System/6000 POWERserver 970 and SPEC SDM KENBUS performance for selected RS/6000s are now available from HONE COMP and the PEC TOOLS disk. The following is a summary of current RS/6000 performance ratings. Benchmark(metric) 220 320H 340 350 520H 530H 550 560 970 ----------------- ---- ----- ---- ---- ---- ---- ---- ---- ---- SPEC 1(geo mean) SPECmark89 25.9 43.4 56.6 71.4 43.5 59.9 75.9 89.3 100.3 SPECint89 17.5 21.8 28.8 36.2 21.8 29.2 36.8 43.8 49.3 SPECfp89 33.7 68.8 88.8 112.3 68.9 96.7 123.0 143.5 160.9 SPEC CINT92(geo mean) SPECint92 15.9 20.9 27.7 34.6 20.9 28.2 35.4 42.1 47.1 SPEC CFP92(geo mean) SPECfp92 22.9 39.4 51.9 65.0 39.6 57.5 71.7 85.5 93.6 Linpack(MFLOPS) 100x100 Double-P 6.5 11.7 14.8 18.6 11.5 20.2 25.6 30.5 30.7 100x100 Single-P 7.6 13.3 17.6 22.0 13.3 19.5 24.4 29.4 29.4 1000x1000 TPP 14.0 37.2 49.0 61.4 37.1 55.4 69.7 83.6 83.8 LIVERMORE LOOPS Maximum Rate 15.6 38.7 51.8 64.7 38.7 52.9 66.2 80.9 81.7 Average Rate 6.3 12.8 17.1 21.4 12.9 17.5 21.9 27.0 27.1 Geometric Mean 5.1 9.3 12.4 15.5 9.3 12.7 15.9 20.1 20.2 Harmonic Mean 3.8 6.3 8.4 10.5 6.3 8.6 10.8 14.4 14.5 Minimum Rate 0.8 1.3 1.8 2.3 1.3 1.8 2.3 3.5 3.5 SPEC SDM(peak throughput, scripts/hr) sdet n/a 140.1 184.6 227.4 140.3 188.9 236.2 271.3 326.0 kenbus1 n/a . . 1479 . . . 1899 2238 TPC-A (Informix standalone) TPS n/a n/a n/a n/a 31.0 42.0 51.0 61.0 K$/TPS n/a n/a n/a n/a 13.9 14.8 13.9 14.2 TPC-A (Client-Server Informix) TPS 72.0 100.9 K$/TPS 12.7 12.4 TPC-B TPS n/a 41.4 56.4 66.9 44.7 52.6 69.2 80.1 110.3 K$/TPS n/a 2.5 2.4 2.2 2.4 2.7 2.9 2.7 2.8 AIM APR II AIMs 16.3 22.6 28.4 36.2 22.4 29.7 36.6 45.3 49.9 ULR 147 202 247 281 198 251 319 418 454 NOTES: Values shown above are the results of development-level systems. While these values should be indicative of generally-available systems, no warranties or guarantees are stated or implied by IBM. IBM recommends application-oriented testing for performance prediction and offers the above commonly reported benchmarks only as an initial indicator. Additional information on these tests are available from your IBM local Branch Office or IBM Authorized Reseller. All measurements using AIX 3.2 except the 320H, 530H and 550 TPC-B which were measured using AIX 3.1.5. SPEC 1, CINT92, CFP92 and LINPACK are CPU intensive benchmarks. SPEC CINT92 and CFP92 are the newly announced CPU intensive integer and floating point benchmark suites. SPEC SDM is a multi-tasking software development benchmark suite. KENBUS numbers are rounded to the nearest whole number. TPC Benchmark A is a multi-user OLTP benchmark. TPC Benchmark B is a multi-tasking database server benchmark. AIM Benchmarks are multi-tasking UNIX benchmarks.  RS/6000 Performance on HONE COMP -------------------------------- HONE COMP contains descriptions of the benchmarks and performance ratings in tables for IBM and competitive systems. Benchmark Document name ----------------------------- ---------------------------------- TPC - A and B TPC Benchmarks A and B Perf. Data SPEC 1.0, CINT92 & CFP92 UNIX Wkstn Perf. : SPEC Benchmarks AIM UNIX System Perf. : AIM Benchmarks Dhrystone 1.1, 2.1, MIPS, UNIX Wkstn Batch Comp. Int. Perf. Whetstone, Linpack, Livermore Loops and Khornerstone Graphics (PLB, X11PERF) RS/6000 & UNIX Wkstn: Graphics Perf. RAMP-C RAMP-C Performance Data Neal Nelson UNIX Sys. Perf. : Neal Nelson Benchmarks How to access PEC performance data on HONE COMP: ------------------------------------------------ 1) Access and logon to HONE, 2) Type 'comp' and press enter on HONE main menu, 3) Type 'pec' in the category field in the COMP main menu and press enter, 4) Select the article by number. RS/6000 Performance on PEC TOOLS -------------------------------- The following documents on the PEC TOOLS disks are being updated and are either already available or will be on or before 04/27/92. FILE NAME DESCRIPTION --------- -------------------------------------------------------- SPECRES Table of IBM & Competitive SPEC 1 results to date SPECALL RS/6000 SPEC Suite 1 press release result sheets CINTRES Table of IBM & Competitive SPEC CINT92 results to date CINTALL RS/6000 SPEC CINT92 press release result sheets CFPRES Table of IBM & Competitive SPEC CFP92 results to date CFPALL RS/6000 SPEC CFP92 press release result sheets RS6CIP RS/6000 Compute Intensive Performance VS Competition - Linpack, SPEC Suite 1, CINT92 and CFP92 SDM10RES Table of IBM & Competitive SPEC SDM results to date SDM10PRF RS/6000 SPEC SDM Performance VS Competition SDM10ALL RS/6000 SPEC Suite SDM press release result sheets RS6TPCAB RS/6000 TPC Benchmark A and B Performance VS Competition TPCABRES Table of IBM & Competitive TPC-A and B results to date TPC6FDA4 RS/6000 970 Informix TPC-A Full Disclosure Report TPC6FDB3 RS/6000 970 Informix TPC-B Full Disclosure Report RS6KPB RS/6000 Performance Brief AIMALL AIM results in Aim APR II format for all RS/6000s How to access performance data on PEC TOOLS ------------------------------------------- To obtain a copy of a PEC TOOLS package, please issue the following command from your PROFS/CMS command line: TOOLS SENDTO DALVM41B TOOLS PEC GET PACKAGE using the actual package name (for example RS6CIP) instead of . To receive updates automatically, subscribe to these packages using the following command: TOOLS SENDTO DALVM41B TOOLS PEC SUB PACKAGE using the actual package name (for example RS6CIP) instead of . ALTERNATELY, you may use the TOOLCAT facility. Please see the 'PEC Performance Index' article on HONE COMP for detailed instructions on the Toolcat facility which makes it easier to access and subscribe to PEC TOOLS documents. If there are any questions, please send a note to PEC at DALVM41B. ====================================================================== >(I)92148. National Language Version Of X3270 Beta version available X3270 is a program product which allows a Risc System/6000 or Sun 4 system to gain 3270 access into a TCP/IP S/370 mainframe. The product allows a user to use host based text and graphical applications on an X-Window capable device. X3270 Version One was limited to work with the United States national language environment, and was only commonly available in the US. A second version of this program has now been produced for Single Byte Enabled (SBCS) language environments. An opportunity for you to use this product internally within IBM has arisen allowing for early verification of this product in your local language. To obtain a copy of this early code, extract the x3270-r2 package from the APPSDISK using the standard tools commands. APPSDISK is located at userid XPRODSOL on node KGNVMA. The following command can be used to get this package: tools sendto kgnvma xprodsol appsdisk get x3270-rs package If you encounter problems whilst using x3270 in your local language environment, then please feed-back this to the product developer contact who can be reached at MEEHAN at KGNVMA. Regards - Mark ====================================================================== >(U)92149. PS/2 ITBU and '/etc/backup' inefficiency Still wondering why '/etc/backup' can't dump more than 40 MB to an 80 MB (DC2080) or 120 MB (DC2120) tape cartridge in an ITBU? If so, then read on. It turns out that the 'backup' program (when invoked with -f/dev/rst0) defaults to a tape density (d) of 700 bytes per inch and a tape length (s) of 4500 feet. That works out to a limit of 36,000 1K blocks per tape cartridge. In other words, 'backup' does not automatically determine the type of cartridge installed and write an amount of data appropriate to the installed cartridge. The documentation tells us we CAN'T change the density parameter or the tape length parameter when used with the ITBU. This morning I tried playing around with the -d and -s parameters and I can now say that the documentation is wrong. It is possible to tweak these values and have 'backup' use much more of the tape cartridges. There are several known facts: The ITBU hardware uses 32 data tracks. A DC2080 tape is 205.0 feet long, therefore use -s 6560. A DC2120 tape is 307.5 feet long, therefore use -s 9840. A little on the conservative side, I want 'backup' to use only 75 MB of a DC2080 tape and 115 MB of a DC2120 tape (to allow for bad blocks which should be formatted out). So ... Total Capacity = tape density * tape length * 12 tape density = Total Capacity / (tape length * 12) = 75 MB / (6560 * 12) = approximately 1000 bytes per inch The tape density is the same for both DC2080 and DC2120 tapes, the in- creased capacity is due only to the increased tape length. - - - - - - - - - - Cut here for future reference - - - - - - - - - - - For DC2080 tapes: find . -print | /etc/backup -s 6560 -d 1000 -i -v -f/dev/rst0 For DC2120 tapes: find . -print | /etc/backup -s 9840 -d 1000 -i -v -f/dev/rst0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Don Reif in Rochester, MN ====================================================================== >(I)92150. AADU 2.1, PC/3270 and Netware can coexist, can't they??? I have been trying and trying and finally manage to make all three basic IBM applications work together sharing the same adapter simultaneously. A lot have been written about this coexistance or compatibility, and I think the configuration and scenario that I'm going to explain is not "officialy" supported but it works for me. It seems that the coexistance mentioned in the plet of AADU 2.1 is finally a true coexistance: you don't have to reboot your PC or unload one program in order to run the other one. I will like everyone interested in this kind of configuration to try and test this with different HW (ethernet) or to tune the configuration in order to free up some more conventional memory. And give feedback (feel free to ask every detail you deem pertinent via this forum or via prof). I wish someone could post here official statement in order to know if we can or not officialy sell and support this type of connectivity solution. I will try to give as much information as it's needed in order to run the following three programs simultaneously sharing the same adapter: 1. AADU version 2.1 2. Personal Communications 3270 for DOS version 2.0 3. Netware DOS Shell (netx)(with ODI lansup driver)" SCENARIO: MACHINE: PS/2 Mod.80-M81 Token Ring 16/4 adapter/A DOS 4.0 installed LAN Support Program vers ion 1.25 DOS Servers on the token ring LAN . 1 or several Risc6000 with AIX3.1.5 or 3.2 . 1 or s veral PS/2 with AIX PS/2 v1.2.1 . 1 or several RT with AI X 2.2.1 Netware Server: . 1 or more Risc 6000 with AIX 3.2 and Netware for AIX/6000 installed and configured with TOKEN-RING frame type. VM connection: . The 3270 connection is made through a 3745 on the token-ring. INSTALLATION: 1. Install and run the servers: DOS Server: pci.obj modules (don't forget the links Netware/6000: (use the TOKEN-RING frame type) (I've tried with TOKEN-RING_SNAP but didn't work) VM (VTAM) you need to have defined in VTAM the fo- llowing parameters: IDNUM, IDBLOCK, LOCATION and nd{ DESTINATION ADDRESS 2. Install DOS 4.0 on the PC 3. Install LAN Support Program v1.25 on the PC 4. Install PC/3270 v2.0 for DOS 5. Install AADU v2.1 choosing PCLAN.DRV 6. Update AADU with fix IX19085 7. Install the netware shell with ODI drivers taken from the ODIUP5 PACKAGE on NWARE386 PCTOOLS disk. 8. Make some changes in Config.sys and autoexec.bat and good luck ************** CONFIG.SYS *************************************** COUNTRY=034,437,c:doscountry.sys shell=c:command.com /P /e:512 rem * LAN Support Program version 1.25 rem * installed for token ring in Spanish environment answering Yes rem * to all questions about Netbios, 3270 etc... device=lansupDXMA0MOD.SYS 034 device=lansupDXMC0MOD.SYS device=lansupDXMT0MOD.SYS es=2 est=2 rem Aix Access for DOS Users version 2.1 rem the bridge.drv is a 52276 Bytes file device=C:PCIDRIVERSBRIDGE.DRV rem pclan.drv is the one that comes in ix19085 wich size is 11136 Bytes rem ask your defect support center device=C:PCIDRIVERSPCLAN.DRV rem * END of CONFIG.SYS ********************** AUTOEXEC.BAT ******************************* rem to check for errors in config.sys e cho END of config.sys pause REM following 3 lines inserted by AADU Install program" set pcipath=C:PCIBIN path %pcipath% set pcipath= rem probably this path can be improved rem be carefull between LOGIN from AADU and from Netware path = C:dos;c:e3;c:tools;c:;c:netware REM following 3 lines inserted by AADU install program set pcipath=C:PCIBIN path %path%;%pcipath% set pcipath= rem following three lines inserted manually for Spanish keyboard rem and 850 code page support (surely can be improved) nlsfunc KEYB SP 850 chcp 850 rem following 6 lines inserted at DOS 4.0 installation ECHO OFF CLS DATE TIME VER PROMPT $P$G rem following 7 lines inserted by AADU install program set EMPATH=C:PCI set LCSPATH=C:PCILIB set NLSPATH=C:PCI%%N%%L.%%C set HOSTS=C:ETC set LANG=En if exist C:PCIEM.SES del C:PCIEM.SES PCIINIT REM lines inserted manually for Netware shell for DOS REM the files were taken from the NWARE386 on PCTOOLS (ODIUP5 PACKAGE) c: cd netware rem lsl.com version 1.20 ( 7648 Bytes) lsl rem lansup.com version 1.20 ( 14094 Bytes) lansup rem ipxodi.com version 1.20 ( 20903 Bytes) ipxodi rem netx.com version 3.22 ( 51201 Bytes) netx REM following line inserted by PC/3270 install program CALL C:$PC3270.BAT REM ******END OF AUTOEXEC.BAT******************************** MEMORY ISSUES: All these TSR and programs leaved free only 150 KB of DOS conventional memory but I can unload PC3270 and netware ODI drivers (with u option) provided I do it in the reverse order they've been loaded. Another thing that can be done is installing a memory manager like QEMM or 386MAX (I wish someone could try it and evaluate the amount of memory freed). At present my machine is full of adapters (2 SCSI, TR, 3270,2 Dual Async, 6157) so I don't think I can optimize a lot but if you use a simpler HW configuration with less adapters probably you could leave more conventional memory for applications. Hope all this can be helpful since it is a full IBM solution. It works for me but the main point now is: is this officially supported ? Can we sell this ? Ivan Montesino (83823465 at SPAVM1) AIX Support Center Madrid, Spain ====================================================================== >(U)92151. HOTW: Breaking/Wrapping Lines The FOLD command breaks/wraps lines in files (or stdin) to a specified width. (The default width is 80). Example: $cat foo.txt 012345678901234567890123456789012345678901234567890 abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ $fold -26 foo.txt 01234567890123456789012345 6789012345678901234567890 abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ See the -w option for breaking at spaces.... Dough Ranz ====================================================================== ====================================================================== >From the jargon file: lobotomy: n. 1. What a hacker subjected to formal management training is said to have undergone. At IBM and elsewhere this term is used by both hackers and low-level management; the latter doubtless intend it as a joke. 2. The act of removing the processor from a microcomputer in order to replace or upgrade it. Some very cheap clone systems are sold in `lobotomized' form --- everything but the brain. >92.05.18 Table of contents: (I)92168. CEADS does not like dials and lpfks on serial lines (U)92169. DO NOT INSTALL MICROCODE ref SGVR8 ON AIX 3.2 SYSTEMS (I)92170. OPEN SYSTEMS NETWORKING: THE TECHNICAL COMPUTING MODEL ON MKTTOOLS (I)92171. AIX V3.2 NETWORK TUNING GUIDE (I)92172. New redbook for diskless machines draft copy available (I)92173. RISC System/6000 CONFIGURATOR CFREPORT FILES (I)92174. AIX V3.2 BLOCK MULTIPLEXER PERFORMANCE RESULTS (I)92175. A glimpse of future networks (I)92176. Finding things on the Internet (U)92177. 3151 emulation over DOS TCPIP V2| (I)92178. Catia performance doc available (U)92179. Cut and paste under AIXwindows 3.2 (U)92180. Problems with upgrade to 3.2 and spread pagingspace (U)92181. X11r5 for the RT running AIX 2.2.1 (U)92182. More on AIX memory usage (U)92183. HOTW: Join two files using a relational-like lookup operation ====================================================================== >(I)92168. CEADS does not like dials and lpfks on serial lines FROM CAEDS FORUM appended at 22:03:07 on 92/02/20 GMT (by NWILLIAM at DFWVM04) I have confirmed with two separate SEs and their accounts that the X-protocol problem that CAEDS has been having is due to having the dials and lpf keys installed via the serial ports. So if you are using other CAD products that call for the dials or lpf keys, and have them installed via the serial ports, then they will need to be physically removed before CAEDS is functional. This does not occur if the dial and lpf keys are connected via the GIO adapter. Nellie Williamson ====================================================================== >(U)92169. DO NOT INSTALL MICROCODE ref SGVR8 ON AIX 3.2 SYSTEMS The European code distribution center started shipping an SCSI microcode update recently. This update is for 3.1 systems only. Do not install it on 3.2 systems| This is what the label on the floppy says: REFERNCE NO SGVR8 PROGRAM 5750-ACG FEATURE 2040 SCSI I/O CNTL AIX/6000 V3 REFER. TO DOCUM. 200B00 RELEASE/LEVEL 01.05 VOLUME OF VOLUME 1/1 If install this on 3.2 you end up with the famous 552 LED code| The foillowing procedure might be helpful if you run into this problem: =============================================================== Circumvention to solve the problem LED 552 after installation of the microcode REFERENCE NO : SGVR8 on a system AIX 3.2 1) boot from distribution tape and chose option 4 ( maint mode ) 2) getrootfs hdisk? ( where ? is the number of the harddisk that contains to the root volume group ) 3) cp -p /etc/methods/cfghscsi /etc/methods/cfghscsi.bad 4) cp -p /etc/methods/cfgchk /etc/methods/cfgchk.bad 5) cd / 6) tctl -f/dev/rmt? rewind 7) tctl -f/dev/rmt?.1 fsf 3 8) tar -xvf /dev/rmt?.1 ./usr/lib/methods/cfghscsi ./usr/lib/methods/cfgchk ( where ? is the number that specifies the tape device ) 9) bosboot -a -d /dev/hdisk? -l /dev/hd5 -u ( where ? is the number that specifies the boot device ) 10) savebase -v 11) key in NORMAL position 12) shutdown -Fr (Thanks to frank kraemer) ====================================================================== >(I)92170. OPEN SYSTEMS NETWORKING: THE TECHNICAL COMPUTING MODEL ON MKTTOOLS This guide will help you with connectivity and interoperability using computing systems such as PCs, RISC System/6000s and mainframes. In addition, clustering RISC System/6000s, IBM storage products and IBM Business Partner products are discussed. To get a copy of this guide enter the following at the OV/VM command line: TOOLCAT MKTTOOLS GET STCBOOK PACKAGE or TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET STCBOOK PACKAGE Procedures for obtaining files from MKTTOOLS vary depending on what system you are running on. If these commands do not work on your system, please contact your Help Desk or End User Support group to find out the procedure for obtaining MKTTOOLS files on your system. To discuss the content or if you have questions on the content of the guide contact Ric Yudico at T/L 752-7248 or DFWVM04(YUDICO). ====================================================================== >(I)92171. AIX V3.2 NETWORK TUNING GUIDE The AIX V3.2 Network Tuning Guide is now available on the AIXIC Tools Disk. This guide explains the function of the mbuf pools and their effect on performance. The mbuf management facility is discussed, as well as the various parameters that can be tuned. Parameters such as lowmbuf, lowclust, mb_cl_hiwat, and thewall as well as the "no" command are included in the discussion. The document explains why to tune the mbuf pools, when to tune them, and how to tune them. To access this file type in : TOOLS SENDTO DALVM41B TOOLS AIXIC GET NETTUNGD PACKAGE The file is a GML script file, thus it can be printed using script. Questions on this notice are to be forwarded to: DALVM41B(SALINAS) ====================================================================== >(I)92172. New redbook for diskless machines draft copy available AIXTOOLS: Information: GG243858 PACKAGE created by KOEPP at AUSVM8. ITSC diskless redbook, draft Get it from your nearest AIXTOOLS shadow with TOOLCAT AIX ====================================================================== >(I)92173. RISC System/6000 CONFIGURATOR CFREPORT FILES May 13, 1992 Because of the assignment of default feature codes to standard memory and disk on the RISC System/6000, CFREPORT files created before 3/12/91 may no produce valid results when used with the CFRS6000 configurator. Any CFREPORT files with a date prior to 3/12/91 should be deleted and re-created prior to use. Questions on this notice should be sent via HONE FEEDBACK. This might be US only| ====================================================================== >(I)92174. AIX V3.2 BLOCK MULTIPLEXER PERFORMANCE RESULTS AIX V3.2 Block Multiplexer Adapter Performance Results are now available on HONE COMP. This document details the results of testing completed in a non-TCP/IP environment from a RISC System/6000 to MVS/ESA. Throughput rates are shown from the workstation through the adapter over a 4.5M channel to memory and to tape. The document also shows the results of testing executed in a TCP/IP environment using the file transfer protocol (FTP) from a RISC System/6000 to VM TCP/IP V2R2 across a 3M channel. In addition, results from a RISC System/6000 across a 16Mbit Token Ring LAN to a RISC System/6000 acting as a gateway to VM TCP/IP V2.2 are shown. Finally, some hints and tips on configuring the adapter are discussed. To access this item from COMP, use VENDOR=IBM, PRODUCT=RISC, and SEARCH WORDS=block multiplexer (note spelling of "multiplexer.") Questions on this notice are to be forwarded to: DALVM41B(SALINAS). AIX V3.2 BLOCK MULTIPLEXER PERFORMANCE RESULTS - PART II AIX V3.2 Block Multiplexer Adapter Performance Results, Part II are now available on HONE COMP. This document details the DRAMATIC PERFORMANCE GAINS, IN THE ORDER OF 250-370%, which can be achieved by changing the TCP/IP window sizes from the defaults on VM TCP/IP and on the RISC System/6000. The document shows the results of testing executed in a TCP/IP environment using the file transfer protocol (FTP) from a RISC System/6000 to VM TCP/IP V2R2 across a 3M channel. In addition, the procedures necessary for changing the window size on both systems is shown. To access this item from COMP, use VENDOR=IBM, PRODUCT=RISC, and SEARCH WORDS=block multiplexer (note spelling of "multiplexer.") Questions on this notice are to be forwarded to: DALVM41B(SALINAS) ====================================================================== >(I)92175. A glimpse of future networks (Ok, its not directly AIX related, but wow, what a speed| afx) IBM and Rogers Cablesystems to Begin Testing Technology for Interactive Digital Services May 14, 1992 (US NEWS) IBM and Rogers Cablesystems today announced that this month they will begin testing technologies that will deliver a new generation of communications, interactive video, entertainment, text and multimedia information. IBM and Rogers will soon test a gigabit (one-billion-bits-per-second) network which couples Rogers' metropolitan area networking facility in Toronto with leading-edge networking systems developed by IBM. The network will be capable of transmitting 30,000 single-spaced pages of information per second -- 500 times the speed of most information networks today. Such high speeds are key to delivering a wide range of digital services to anyone on the network. The field test is the first implementation of a joint study, announced by the two companies in October 1991, aimed at developing and refining high-speed networking technologies. In the first phase of the field test, to be completed by mid June, the MAN (Metropolitan Area Network) will connect two buildings in metropolitan Toronto. The MAN will consist of a high-bandwidth fiber optic ring and IBM RISC System/6000 workstations equipped with IBM's new gigabit local and metropolitan area network adapters. For testing purposes, the MAN initially will support simple data applications, such as high-speed file transfer between two users. By late summer, additional sites will be added, and interactive multimedia applications, such as full-motion desktop videoconferencing, will be operational. Later this year, IBM's PARIS switching systems will be installed. PARIS features switching speeds of up to 6 gigabits -- 200,000 single-spaced typed pages -- per second. This technology will enable the MAN to be extended to support dozens of buildings and hundreds of users. Rogers Cablesystems is the largest cable television service provider in Canada, serving approximately 1.8 million customers in Ontario, Alberta and British Columbia. ====================================================================== >(I)92176. Finding things on the Internet Subject: "Panning the Internet river for nuggets of gold" Source: Network World, 4/20/92, pg 31, Skip MacAskill What do the following have in common: - satellite photos of the Earth - pictures of a space launch - income tax programs - the most recent grants from the Nat'l Science Foundation The answer is they all can be gotten from the Internet o the task of finding what lies where isn't easy - Jerry Martin created a comprehensive resource guide to the net - he runs the Network Information Center at Ohio State Univ. o "There's so much information available on the Internet, it is almost impossible to know where things are. I wrote this document because I needed it. It will help newcomers bypass the research phase that most of us experienced in finding our way around" Martin o researchers find the guide a boon to find: - grant opportunities - science and technology information systems - information databases and libraries and more The Guide is a top-level index - a list of lists with highlights of referenced files o "A number of reference guides are available to users for specific areas of the Internet, but this is the first one that acts more as a pointer to where different types of information can be found. The guide attempts to make the process of hunting down information on the Internet more manageable, which isn't an easy task because the way information is gathered changes so rapidly" Martin Source: via anonymous ftp at magnus.acs.ohio-state.edu Directory: pub/network File: resource.txt Author: Jerry Martin NIC@osu.edu Academic Computing Services The Ohio State University IBM internal availability: TOOLS SENDTO ALMVMA ARCNET NETFORUM GET RESOURCE OTHERNET Norm deCarteret Information Network Tampa FL ====================================================================== >(U)92177. 3151 emulation over DOS TCPIP V2| Wow, I'm really excited about this, so I thought I'd spread the word... Yesterday I worked over the phone with Bob Frittelli of RD Enterprises in getting his E3151PC emulation program working over IBM's TCP/IP for DOS Version 2, and I am thrilled to report that it works like a champ. It works very much like PROCOMM with its popup windows for system settings, colors, phone numbers, DOS shell, file transfer, etc. What I needed it for was the 25-line screen for HCON connections, and that works great (heck, I even have 50 lines if I want to)... The great thing about it is that it offers CONSISTENCY... customers no longer have to deal with any dreaded VTxx emulations, function keys can have consistent definitions whether you are dealing with real or emulated 3151s, and E3151PC not only works over IBM TCP/IP for DOS V2, but also serial, AADU, PC/TCP, and LWD and NVT connections. At $210 for a 1-50 user site license, it's also unbelievably priced| Call Bob directly at 407-831-6118 for more info. His fax number is 407-830-8506 (send to ATTN: RD Enterprises - Bob Frittelli). Note: Others mentioned in the fora that the emulation is not stable enough. So check it out first. If it works, it looks like a great tool to me. afx ====================================================================== >(I)92178. Catia performance doc available For those of you interested in CATIA performance Al Levit has found the following. Please note that a document presented at COE '92 on CATIA performance is now available. You can obtain a copy by issuing the following command from our PROFS: TOOLS SENDTO DALNESSC TOOLS CADINFO GET CATPERF1 PACKAGE Iain Elliot ====================================================================== >(U)92179. Cut and paste under AIXwindows 3.2 From: hublerhercules.lerc.nasa.gov (Dale Hubler) Newsgroups: comp.unix.aix Organization: NASA Lewis Research Center >2. I just discovered while trying to write this post using emacs > on another (non-IBM) machine (SUN) that I can't cut & paste > from an AIXterm window into the emacs window (i.e. mark area > start in the AIXterm window with the left mouse button, mark > area stop with right mouse button, and then move to the emacs > window and place the cursor with the left mouse button and > insert the region of text marked in the AIXterm window using the > middle mouse button...This worked fine with AIX 3.1.5, now > since upgrading to 3.2 I can no longer do this...same thing happens > when I try running emacs on the same machine as the AIXterm. > I'm using GNU Emacs 18.57, and am getting pretty frustrated with > AIX 3.2 My emacs user fixed it with this in the .Xdefaults file (thanks to Brian) aixterm.Translations: #override Shift Ctrl Meta : select-end(CUT_BUFFER0,PRIMARY)n Shift Ctrl Meta : insert-selection(CUT_BUFFER0,PRIMARY)n Shift Ctrl Meta : select-end(CUT_BUFFER0,PRIMARY)n Shift Ctrl Meta : select-end(CUT_BUFFER0,PRIMARY)n Shift Ctrl Meta : select-end(CUT_BUFFER0,PRIMARY)n Shift Ctrl Meta : insert-selection(CUT_BUFFER0,PRIMARY)n -- Dale A. Hubler -- Sverdrup Technology -- (216) 977-7014 hublergalaxy.lerc.nasa.gov Progress marches on, trampling everything in its path ====================================================================== >(U)92180. Problems with upgrade to 3.2 and default logical volume names From: packacd.acd.ucar.edu (Daniel Packman) Newsgroups: comp.unix.aix Organization: Ntl Center for Atmospheric Research, Atmospheric Chemistry Another caveat for the 3.2 upgrade... The installation procedure determines if you have a 3.1 system that can have a "Preservation Install" option by checking to see if the logical volumes in rootvg named hd2, hd3, hd4, hd5, hd6 and hd8 exist. If any of these 6 logical volumes does not exist, booting off the tape will bypass the screen giving you a chance to do a Preservation Install.  In our case, we went through a procedure to recreate the paging logical volume (in order to decrease it and create others on other physical volumes). Smit created one with the name 'paging00'. We had to do the following: $ chps -a n paging00 # deactivate this on reboot, we $ # If you have no other paging space, you will need to create a $ # new paging space for reboot $ shutdown -Fr #reboot quickly so users don't notice :-) $ chlv -n'hd6' paging00 # rename paging space to the standard one $ chps -a y hd6 # activate this for reboots $ swapon /dev/hd6 # activate this now -- Dan Packman NCAR INTERNET: packncar.UCAR.EDU (303) 497-1427 P.O. Box 3000 Boulder, CO 80307-3000 DECNET SPAN: 9583::PACK ====================================================================== >(U)92181. X11r5 for the RT running AIX 2.2.1 From: brantleyis.rice.edu (Michael Francis Brantley) Newsgroups: comp.sys.ibm.pc.rt,comp.unix.aix Organization: Rice University I've made a complete distribution of X11R5 binaries for AIX 2.2.1 on the IBM RT available via anonymous ftp, along with a patch file that represents the changes needed to get the source to compile. The X server is not perfect - but it is very useable and with the source you may be able to fix the few problems that are left. Nor is the patchfile perfect - you'll probably need to selectively massage the Makefiles and do other backflips to make it do its trick. To get the built binary distribution, get the files: brazos.is.rice.edu:/pub/aix_rt/X11R5.bin/* ... and follow the directions as described in the README.R5 file. To build the source using my patch file, get the files: brazos.is.rice.edu:/pub/aix_rt/X11R5.src/* ... and follow the instructions in the AIX_R5_Patch file. Please let me know about problems you have, and though I won't be working between May 15 and Jun 8 I'll still try to respond to any problems you may have. Good Luck ||| Michael Brantley Currently (Until May 15) Soon to be (Beginning June 8) --------------------------------- ------------------------------------ O.N.C.S. Department of Computer Science Rice University, Houston Texas Princeton University, Princeton, NJ (brantleyrice.edu) (brantleyprinceton.edu) ====================================================================== >(U)92182. More on AIX memory usage From: MCOGCHVM1.VNET.IBM.COM ("Michael A. Coggins") Newsgroups: comp.unix.aix A lot of people have been asking questions about AIX RAM and virtual memory utilization, and I'll try to shed some light onto the subject. First, I would like to clarify that I am not one of the people that either wrote or designed this code, so there may be some flaws in my analysis. Q1) Why does vmstat show no free RAM pages? A1) AIX uses RAM as a possibly huge disk buffer. If you read a file in the morning, that file is read into RAM, and left there. If no other programs need that RAM, that file will be left in RAM until the machine is halted. This means the if you need the file again, access will be quick. If you need that RAM, the system will simply use the pages the file was using. The pages were flushed back to disk earlier. This means that you can get a huge speedup in disk access if you have enough RAM. For example, a 200MB database will just ease into RAM if you have a 256MB system. Q2) Since vmstat shows no free RAM pages, am I out of RAM? A2) Probably not. Since disk files will be "mapped" into RAM, if vmstat shows lots of RAM pages FREE, then you probably have too much RAM (not usual on a RISC System/6000)||| Q3) Shouldn't the "avm" and the "fre" fields from vmstat add up to something? A3) No. The avm field tells you how much "Active Virtual Memory" AIX thinks you are using. This will closely match the amount of paging space you are using. This number has *ABSOLUTELY* nothing to do with the amount of RAM you are using, and does *NOT* include your mapped files (disk files). Q4) Why does the "fre" field from vmstat sometimes show lots of free RAM pages? A4) This will happen after an application that used a lot of RAM via "working" storage (not NFS storage, and not disk file or "persistent" storage) exits. When RAM pages that were used by working storage (a program's stack and data area) are no longer needed, there is no need to leave them around. So, AIX just completely frees these RAM pages. The time to access these RAM pages vs. a RAM page holding a "synced" mapped file is almost identical. Therefore, there is no need to periodically "flush" RAM. Q5) Is the vmstat "fre" field useful? A5) The vmstat "fre" field only tells you the sum of the virtual memory you are currently using and the sizes of the files you have accessed since you booted subtracted from the RAM size. Simpler, if the number is consistently small (less than 500 pages), this is normal. If the number is consistently large (greater than 4000 pages), then you can take out one 16MB RAM card, and put it in another machine. Q6) Does AIX use more paging space than other unix systems? A6) Here is a slightly edited version of a posting I put on one of our internal newsgroups recently. It is somewhat long-winded, but hopefully it will add some insight. To summarize: Under many scenarios, AIX requires more paging space than other "normal" unix systems. Let me explain why, and give a couple of examples. The AIX VMM implements a technique called "early allocation of paging space". When a page is allocated in RAM, and it is not a "client" (NFS) or a "persistant" (disk file) storage page, then it is considered a "working" storage page. Working storage pages are commonly an application's stack, data, and any shared memory segments. So, when a program's stack or data area are increased, and RAM is accessed, the VMM will allocate space in RAM and space on the paging device. This means that even before RAM is exhausted, paging space is used. This does not happen on many other unix systems I know of, although they do keep track of total VM used. Example 1: workstation with 64mb RAM is running only one small application that accesses only a few small files. Everything fits into RAM, including all accessed data. On AIX, some paging space will already be used. On the other systems, paging space will be 100 percent free. Clearly, this is an example that shows where we use more paging space than the other machines. Next, an example where the paging space requirements are almost the same. Example 2: Same machine as above, except we are running in an environment where many applications are running, and RAM is "overcommitted" (there isn't enough RAM). Also, in this environment, the system is running applications that are started, run, left idle, and not in constant use. A session of FRAME running in a window, for example. What happens is that eventually (theoretically) all applications will be paged out at least once. On the AIX system and the other systems the total paging requirements will be the same (assuming similar malloc algorithm). The major difference is that the AIX system allocated the paging space pages before they were actually needed, and the other systems did not allocate them until they were needed. However, most other systems have an internal variable that gets incremented as virtual memory pages are used. AIX does not do this. This can cause the AIX system to run out of paging space (virtual memory), even though malloc() continues to return memory. This "feature" allows sparse memory segments to work, but requires that all normal users of malloc() (sbrk()) to know how much virtual memory will be available (actually impossible), and to handle a paging space low condition. A big problem. There are some pretty obvious pros and cons to both methods of doing Virutal Memory. You get to judge which is better. Without understanding the AIX VMM, at best a technical support person will have trouble explaining what is happening to AIX paging space, at worst they will underconfigure a machine, which can lead to crashes (paging space low). Another quick point, I keep hearing the rule of 2x RAM for paging space. This is rather simplistic, as are most "rules of thumb". If the machine is in an enviroment I like to call a "persistant storage environment", meaning that they have a few small programs, and lots of data, they may not need even as much as 1x RAM for paging space. For example, a 1GB database server running on a 6000 with 256 MB of RAM, and only running about 50 MB of "working" storage doesn't need 512MB of paging space, or even 256 MB of paging space. They only need the amount of paging space that will allow all their working storage to be paged out to disk. This is because the 1GB database is mostly "persistant storage", and will require little or no paging space. So, keep in mind that more paging space is not necessarily good, since any unused paging space is simply wasted disk space. *BUT*, if you don't have enough paging space, very bad things will happen to your system. Tip: Don't have more than one paging space per disk. I hope these questions and answers clarify some of the frequently asked questions about the AIX memory management system. Tip: Turn on memory scrubbing in AIX 3.2 chdev -l sys0 -a memscrub=true Tip: Put a lot of RAM in your IBM RISC System/6000 - it will use it. Mickey Coggins IBM dude in CH mcogchvm1.vnet.ibm.com ====================================================================== >(U)92183. HOTW: Join two files using a relational-like lookup operation The JOIN command is a bit like a having an SQL-database-join operation ... without all the pain and $uffering of a RDBMS. The collation (sort) order of the 'key' field is very important. $cat names 313-436 9503 Doug Ranz, 313-552 5977 John Zachos, 614-225 3585 Carol Oswald, 614-225 3650 Rick, Beach, $cat phones.xref 313-436 Dearborn, Michigan 313-552 Southfield, Michigan 614-225 Columbus, Ohio $join names phones.xref 313-436 9503 Doug Ranz, Dearborn, Michigan 313-552 5977 John Zachos, Southfield, Michigan 614-225 3585 Carol Oswald, Columbus, Ohio 614-225 3650 Rick Beach, Columbus, Ohio There are many options for the join command. They permit you to specify output options, matched lines, unmatched lines, collation sequence, etc ... checkout the man page(s). From Dough Ranz ====================================================================== ====================================================================== Please take note of the following new commands: Corrupt everything Corrupt everything twice cc Corrupt disks and crash cds Corrupt disk system areas cdd Corrupt disk user data areas cpc Copy and corrupt crf Create (empty) read-only file cwf Create (empty) write-only file hcf Halt and catch fire help Halt, exit log-in, print dump ibc Ignore backup commands ispn Increment system parameters (default is 100, but any integer may b given as an argument: the command uses a randomized algorithm base on the daily menu of a small cafe in Buenos Aires and the present in Kuala Lumpur to determine whether it recognizes arguments or no and if so what to do with them) inf Initiate network failure irb Inject random bug lbc Load backup and corrupt lli Load, link and ignore lxl Load and execute the system administrator's lunch ppj Print page and jam rap Randomize access permissions rup Randomize user properties rbs Read backup tape and shred rdc Read disk and crash rpm Read programmer's mind scf Simulate cabling fault wdc Write data corrupted xsc Execute system crash xop Execute operator xus Execute user xxx Load and display the system administrator's pornography collection workspace backgrounds zx81 Put the cpu into ZX81 emulation >92.06.02 Table of contents: (I)92184. AIX NETVIEW/6000: NOW AVAILABLE FOR CUSTOMERS (I)92185. PERFORMANCE DATA FOR RISC SYSTEM/6000 220 (I)92186. IBM DATA FACILITY DISTRIBUTED STORAGE MANAGER ANNOUNCED (I)92187. IBM ANNOUNCES FDDI CONCENTRATOR AND WORKSTATION ADAPTERS (I)92188. THE QUICKSIZER/6000 FOR WINDOWS (I)92189. NEW REDBOOKS NOW ON TWO TOOLS DISKS (C)92190. The New HP Monster Servers (I)92191. 970 vs 560 performance in a commercial environment. (I)92192. GETTING STARTED WITH OPEN SYSTEMS (I)92193. NEW AIX INFORMATION ON HONE ASKQ (SETI) (I)92194. LOTUS TO SHIP VERSION 1.2 OF LOTUS 1-2-3 FOR THE /6000 (I)92195. GRAPHICS SYSTEMS CUSTOMER SATISFACTION SURVEY (I)92196. AIX VERSION 3.2 PERFORMANCE MEASUREMENTS FINAL REPORT (I)92197. AIX CASE PRODUCTS AVAILABLE, ON SCHEDULE (I)92198. IBM ANNOUNCES THE 3270 EMULATOR FOR THE X WINDOW SYSTEM (I)92199. Sparcstation 10 (U)92200. AIX 3.2 crontab security vulnerability (U)92201. Shrinking the /usr filesystem on 3.2 (I)92202. AIX 3.1 to AIX 3.2 Upgrade Tools Package for RS/6000 (I)92203. XDM package of configuration files (U)92204. WIT - What Is This (U)92205. HOTW: Join two files using a relational-like lookup operation ====================================================================== >(I)92184. AIX NETVIEW/6000: NOW AVAILABLE FOR CUSTOMERS AIX NetView/6000*, which was announced in January, is now available for your customers. This availability demonstrates an improvement to the published June 26 availability date and is indicative of the tremendous interest and attention the product has received. Additional Enhancements to the January Announced Product These will be available in the shipped product and are listed below: Enhanced Graphics: o New zoom capability lets network operators view the entire topology, or enlarge specific sections of the topology, for easier viewing. This feature is available in both the internet and network views. The enlarged section can be examined using window scroll bars. o Acknowledge capability for making known down nodes non-red o Improved Ping ability (routing option) by sending variable-size packets with user-specified data (assists in finding data-dependent errors) o Traceroute feature included Main Menu Improvements: o The View option can display a summary of statistics about all or a subset of devices in the network, using "Totals" o The Monitor option can collect statistics from remote SNMP nodes by using the new "Mgmt(2)" applications Additional Vendor Support Through the NS Vendor Enablement Program (VEP), considerable progress has been made in regard to vendor support of AIX NetView/6000. IBM is working with both hardware vendors and software developers to ensure that their SNMP enabled devices can be managed by the AIX NetView/6000 thru their Management Information Bases (MIBs), to provide product differentiating applications, and to provide platform enhancing applications. The following companies will ensure that their MIBs and/or applications will operate cooperatively with the AIX NetView/6000 on the RISC System/6000*: Hardware Vendor MIB Support Hardware Products (In Addition to the 10 announced in January) o 3Com Corporation, Santa Clara, CA NETBuilder* TR, II, & more o Ungermann-Bass, Inc., Santa Clara, CA Access/One* with options Hardware Vendor Applications Application Name o Chipcom Corporation ONdemand Network Control Southborough, Mass. System* for NetView/6000 o SynOptics Communications, Inc., Lattis Views* Santa Clara, CA Platform Enhancing Vendor Applications Application Name o Accugraph, El Paso, TX MountainTop* o Bridgeway Corporation, Redmond, WA EventIX* o Metrix Network Systems, Inc., Nashua, NH NetMetrix* These companies join the group of 10 hardware/software developers who announce their participation in the NS Vendor Enablement Program (VEP) in January. The above lists will continue to expand as additional vendors are added. As MIBs are successfully tested, they will be added to the IC Tools disc for extractio by the Field. Watch Natboard for further developments in regard to the VEP, or contact Henry Fernandez in RTP, NC at 919-543-9931 (HFERNAN at RALVMM). Background AIX NetView/6000 network manager was announced January 21 as providing customers with the ability to manage their TCP/IP networks from a RISC System/6000 workstation. AIX NetView/6000 manages those devices containing SNMP agents within a TCP/IP network. It can also monitor all IP-addressable devices, and supports a wide range of multivendor devices, including workstations, mainframes, routers, bridges, and hubs, including the IBM 6611 Network Processor. AIX NetView/6000 provides comprehensive network management for such networks as workgroup and enterprise LAN's. Highlights of the AIX NetView/6000 product include: o Distributed Network Management for stand-alone control with a host o Centralized Network Management (optional) working in conjunction with AIX NetView Service Point to provide 2-way communication with NetView o SNMP Management Applications for Fault, Performance, & Configuration o Easy and fast installation with high usability o Graphics based on X-Windows 11.4* and MOTIF 1.1* o Comprehensive support for the IBM 6611 Network Processor o Several MIB tools for facilitating management of multivendor devices Additional Reference Material o AIX NetView/6000 1/21/92 Networking Natboard Notice, which contained a list of Reference material available and the list of 10 vendors in the VEP o HONE: important new information relating to competition. Do a COMP fastpath and search under NetView/6000 o NetView Forum (see the 4/22/92 update re: Positioned to AIX Network..) o White Paper "LAN Network Manager and AIX NetView/6000", including a set of questions and answers, on Mkttools under DISTMGT (available after May 20) AIX NetView/6000 is priced at $14,900. The Product Number is 5765-077. Accounts with current orders on AAS are encouraged to modify and improve the ship date to correspond to today. * AIX, NetView, RISC System/6000 (RS/6000) are trademark or registered trademarks of IBM Corporation The products denoted by "*" are copyright, trademark, or registered trade- marks of the respective company they are listed beside CONTACT: Tom Streeter (919) 301-3193 (T/L 352) at DALVM41B(STREETER) ====================================================================== >(I)92185. PERFORMANCE DATA FOR RISC SYSTEM/6000 220 NOTE: This is an update to the Performance Data that was published on AIX+RS NATBOARD on May 19. TPC Benchmark B performance data and Graphics performance data for the RISC System/6000 220 is now available on the HONE COMP database. The data is reproduced below for your quick reference. 1) TPC-B data for 220 (perf. in tpsB, price/perf. in K$/tpsB), measurement based on AIX 3.2. 33.19 tpsB, 1.90 K$/tpsB TPC data for other POWERstations/POWERservers published earlier and recently with the 4/21/92 announcement. 2) GPC Picture level benchmark data for 220 GTO <------------------PLBlit : PLBopt--------------> SYSTEM & API pc_ sys_ cyl_ head shuttle Memory/Disk in MB board chassis head --------------------- --------- --------- --------- --------- --------- 220 GTO with graPHIGS 18.5:32.4 29.5:NA 11.3:17.4 27.0:31.8 NP:22.4 16/400 220 GTO with GL 20.9:29.5 9.1:38.2 NR 18.3:27.5 NR 16/400 RS/6000 Software Configuration: AIX V3.2 AIXwindows V1.2 GPC data for other POWERstations/POWERservers as well as a detailed description of the GPC Picture Level Benchmark is available in the HONE COMP document listed below. 3) CATIA and CAEDS performance data for the 220 GTO is available in the HONE COMP document titled "RS/6000 220 & POWER GTO Graphics Performance". RS/6000 Performance on HONE COMP HONE COMP contains descriptions of the benchmarks and performance ratings in tables for IBM and competitive systems. TPC and GPC data can be found in: Benchmark Document name TPC - A and B TPC Benchmarks A and B Perf. Data Graphics (PLB, X11PERF) RS/6000 & UNIX Wkstn: Graphics Perf. CAEDS, CATIA data RS/6000 220 & POWER GTO Graphics Perf. Remember that HONE COMP contains other articles for SPEC, AIM etc. This is a partial list. How to access PEC performance data on HONE COMP: 1) Access and logon to HONE, 2) Type 'comp' and press enter on HONE main menu, 3) Type 'pec' in the category field in the COMP main menu and press enter, 4) Select the article by number. RS/6000 Performance on PEC TOOLS The following TPC documents on the PEC TOOLS disks are being updated and are either already available or will be on or before 05/22/92. FILE NAME DESCRIPTION TPCABRES Table of IBM & Competitive TPC-A and B results to date TPC6FDB5 RS/6000 220 Informix TPC-B Full Disclosure Report Remember that PEC TOOLS contains many other deliverables. This is a partial list. How to access performance data on PEC TOOLS To obtain a copy of a PEC TOOLS package, please issue the following command from your PROFS/CMS command line: TOOLS SENDTO DALVM41B TOOLS PEC GET PACKAGE using the actual package name for example RS6CIP instead of . To receive updates automatically, subscribe to these packages using the following command: TOOLS SENDTO DALVM41B TOOLS PEC SUB PACKAGE using the actual package name for example RS6CIP instead of . ALTERNATELY, you may use the TOOLCAT facility. Please see the 'PEC Performance Index' article on HONE COMP for detailed instructions on the Toolcat facility which makes it easier to access and subscribe to PEC TOOLS documents. If there are any questions, please send a note to PEC at DALVM41B. ====================================================================== >(I)92186. IBM DATA FACILITY DISTRIBUTED STORAGE MANAGER ANNOUNCED May 20, 1991 Yesterday, IBM announced the Data Facility Distributed Storage Manager (DFDSM (TM)), a client/server software product that will provide storage management and data access services for customers in a heterogeneous network environment. DFDSM is the follow-on product to Workstation Data Save Facility/VM (WDSF/VM) and supports existing WDSF/VM clients plus additional client operating systems. The storage management services function of DFDSM allows a MVS or VM system to act as a file backup and archive server for local area network (LAN) file servers and workstations. It features a highly-automated, centrally-scheduled, policy-managed backup and archive system for IBM and non-IBM file servers. It works automatically to retrieve and store data according to a preset schedule, thereby providing storage and protection for an enterprise's information assets. DFDSM supports the latest versions of many operating systems, including DOS, OS/2*, AIX* for the RISC System/6000*, SunOS**, Apple Macintosh**, Novell NetWare** and Microsoft Windows**. DFDSM will be in controlled availability in the fourth quarter of 1992. For more information, contact Art Petrone, TL 351-2413, RHQVM04(APETRO) * Trademark or registered trademark of IBM Corp. ** Trademark or registered trademark of Microsoft Corp., Sun Microsystems, Apple Computer Corp., or Novell Corp. ====================================================================== >(I)92187. IBM ANNOUNCES FDDI CONCENTRATOR AND WORKSTATION ADAPTERS Today IBM announced a suite of FDDI (Fiber Distributed Data Interface) products ranging from FDDI Workstation Adapters, to the 8240 FDDI Concentrator for clustering PS/2s and other devices and network management support via AIX NV/6000 to help ensure network reliability an efficient network utilization. And in the future a graphics application will be available on AIX NV/6000 in addition to the support being announced today. Also being announced is statement of direction for FDDI support on the 6611 router. Based on current ANSI and ISO standards, these FDDI products let you link devices to form a high-performance workgroup LAN at speeds of 100 Mbps, six times faster than Token-Ring, the fastest popular LAN technology. Or you can attach devices to an FDDI backbone that ties together Token-Ring, Ethernet, or FDDI LANs. Cabling options include optical fiber for long distances, or IBM Cabling System shielded twisted-pair wiring for cost-effective connections over shorter distances. These products can dramatically boost end user productivity for new applications such as imaging, business and research graphics, image and data-intensive information for many applications for many industries. Below are the deliverables available on MKTTOOLS to support this announcement: G2213349 PACKAGE--The 8240 FDDI Concentrator and IBM FDDI Workstation Adapters specification sheet. (It can also be accessed through HONE PROPOSAL, HONE DEMOSPRESS and IBMLINK.) LANFDDI PACKAGE--Several key items to present to customers: A paper on a general overview of FDDI. An overview presentation on today's announcement of the IBM 8240 FDDI Concentrator and FDDI adapters. A detailed presentation on the FDDI products. LANCABLE PACKAGE--Has been updated to include a paper on IBM Cabling Specifications for STP for FDDI. This is referenced in the announcement letters dated 5/19. LAN0592 PACKAGE--A set of questions and answers and the press release. Note the 5/12 press release on 11 vendors support for the IBM Cabling System STP is included. DISTMGT PACKAGE--A white paper on IBM's strategy for LAN management titled "The Future of Distributed Management with LAN Network Manager and AIX NetView/6000." Also included are a set of Q&A's. This package will be available on or before 5/21. LANHUB PACKAGE-- An overview presentation of LAN Hubs. To receive the MKTTOOLS packages, enter the following on the command line: TOOLCAT MKTTOOLS GET packagename PACKAGE or for systems without TOOLCAT enter: EX TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET packagename PACKAGE Contact: Joan Rennaker ATLVM1(RENNAKEJ) ====================================================================== >(I)92188. THE QUICKSIZER/6000 FOR WINDOWS MAY 21, 1992 AIX Systems Support is pleased to announce the immediate availability of the QuickSizer/6000 for Windows. The QuickSizer/6000 is a productivity tool that uses empirical workloads, together with performance algorithms, to size the RISC System/6000 under a variety of conditions. It advises the user of an appropriate model, memory, and disk configuration. This version of the QuickSizer/6000 is made available in addition to the DOS version, which will continue to be maintained. The QuickSizer/6000 for Windows offers greatly improved ease of use over the DOS version. Context sensitive and hypertexted help are available at the click of a mouse, while menu-bars, buttons, and other graphical objects permit users to easily navigate within the application. The Quicksizer/6000 for Windows executes on OS/2 2.0 and MS-Windows. The QuickSizer/6000 is for the use of IBM marketing personnel and authorized IBM Business Partners. Usage questions concerning the QuickSizer/6000 will be handled via ASKQ and IBMLink/ASK Support. To obtain a copy of the QuickSizer/6000 for Windows package, type the following from the PROFS command line: TOOLS SENDTO DALVM41B TOOLS AIXIC GET SIZ6KWIN PACKAGE To obtain a copy of the QuickSizer/6000 for DOS package, type the following from the PROFS command line: TOOLS SENDTO DALVM41B TOOLS AIXIC GET SIZE6000 PACKAGE ====================================================================== >(I)92189. NEW REDBOOKS NOW ON TWO TOOLS DISKS The ITSO has recently placed newer Redbooks onto two tools disks on the WTSCPOK system to allow online access. The two repositories are: REDBOOK : The BOOK form collection of recent redbooks REDPRINT : The TERSED LIST3820 versions of recent redbooks The books are stored using their IBM Form Number. For example, the recent Austin Redbook, 'Upgrading to AIX 3.2' (GG24-3814) can be requested in LIST3820 form using the following command: TOOLS SENDTO WTSCPOK TOOLS REDPRINT GET GG243814 PACKAGE It is probably prudent to ensure a copy of the CATALOG is maintained on your local system so that the TOOLCAT utility can be used. Recent AIX Oriented Redbooks available on REDPRINT/REDBOOK -IBM AIX X-Windows/Motif Prog Gde GG24-3382 -AIX V 3.2 National Language Support GG24-3850 -Elements of AIX Security GG24-3622 -RISC/6000 NIC Performance Tuning GG24-3611 -RISC/6000 as a Real-Time System GG24-3633 -Writing a Device Driver for AIX v3 GG24-3629 -IBM Xstation 120/130 GG24-3695 -AIX/V3 X.25 Communications GG24-3692 -Mainframe and Workstation NIC GG24-3676 Software Compatibility -Printing under AIX V3 GG24-3570 -Experience of AIX Netview Service Pt GG24-3700 -Predicting Execution time of RS/6000 GG24-3711 -Upgrading to AIX 3.2 GG24-3814 -AIX Windows v1.2 - 2D features GG24-3813 -3D Computer Graphics Concepts GG24-3836 ====================================================================== >(C)92190. The New HP Monster Servers IBM CONFIDENTIAL This is a special issue of the Mid-Range News from Competitive Marketing Support Centre in Copenhagen, due to the fact that HP yesterday announced new HP 3000 and HP 9000 high end models. HP Corporate Business Servers - "Emerald" launch. ************************************************************************* This document was created on the 20th of May 1992 by Torben Olsen, Program Manager, CMSC, Copenhagen. The content is my personal notes from a 45 minutes presentation of the new HP 3000/900 and HP 9000/890 Corporate Business Servers held by Hewlett Packard at the International HP-Users Conference in Copenhagen. ************************************************************************* CAUTION: People with weak nerves are recommended to have access to a can of cold water, as this is scary reading ************************************************************************* The presentation abstracts told the following: HP goes 'head on' to mainframe suppliers with HP 3000/900 and 9000/890 corporate business servers ************************************************************************* Common characteristics of the HP Corporate Business Servers: 5 new corporate servers are announced for the HP 3000 series and 4 for the HP 9000 series. Shipment will be late August. The models come in a new chassis, about 1,6 m high, looks a lot like a single-rack 9406 AS/400. The chassis holds space for 8 CPU slots, though "only" 4 of them are used in the current top models. The CPU's run at 60 MHz clock rate. The CPU's are air-cooled PA-RISC. Max. memory is 2 GByte. The CPU utilises 2 MB cache and the internal I/O datapath has a bandwidth of 1 GByte. A major improvement. HP calls it the 'Balanced Systems Architecture'. This leads to a performance enhancement by up to 70 percent over the current SMP (Symmetric Multi Processing) products from HP. Maximum number of users is claimed to be 2.300 for the HP 3000 992/400 and 4.500 for the HP 9000 890/400. ************************************************************************* The HP Corporate Business Servers at a glance: The HP 3000 980/100 was used to give a relative performance figure for the 5 new HP 3000 models. The 980/100 runs at 90 tps-A in the TPC-A benchmark. The tps-A figures were announced as the Design Goals for the boxes. IBM CONFIDENTIAL Entry Model: HP 3000 990 is a one processor model. Relative performance: 1,25 tps-A: 114 HP 3000 992/100 has one processor. Relative performance: 1,5 tps-A: 145 HP 3000 992/200 has two processors. Relative performance: 2,6 tps-A: 240 HP 3000 992/300 has three processors. Relative performance: 3,4 tps-A: 330 HP 3000 992/400 has four processors. Relative performance: 4,5 tps-A: 400+ The HP 9000 890 series were labelled with the following figures: HP 9000 890/100, one processor model, tps-A: 110 HP 9000 890/200, two processor model, tps-A: 185 HP 9000 890/300, three processor model, tps-A: 275 HP 9000 890/400, four processor model, tps-A: 336 Comment: Now, these figures are HP's Design Goals. The current HP 3000 980/400 performs only 2.3 times the 980/100. With the figures for the 992/400 HP indicates, that they have succeeded to improve the PA-RISC SMP Architecture to gain 2,8 times the performance of a one processor model. The new series is still not equipped with Superscalar chips, and in the presentation HP was very carefully pointing out, that the figures did not derive from an actual TPC benchmarking. HP said, that they would bring 8-way, superscalar equipped models to the market in 1993, and that they had plans for launching 12- and 16-way SMP models to the market within two years from now. HP said, that the new Corporate Business Servers would NOT replace the current SMP products. The new release of the operating system MPE/iX, 4.0 for the HP 3000 series, shipping in June, has support for these new models. HP told that major improvements has been implemented in this version of MPE/iX, but at the same time they told about a 'coming soon' release 4.5, aimed to meet the 'datacenter expectations' of ease of operation. New features in 4.5 will be: Try/Recover Routine, increased table limits, table monitor and intelligent boot-up. IBM CONFIDENTIAL A new release of HP-UX, 9.0 will hold some standards enhancements and a Logical Volume Manager. HP targets mainframe-customers, who want's to off-load the mainframe with applications to avoid the need for an expensive upgrade. The presenter gave an example, where an IBM-customer had the choice between taking a 10 million USD upgrade from IBM or off-load applications to an HP 3000 server, costing 1,5 million USD. He chose the latter. HP positions the Corporate Business Servers as a space-saving, low-cost, OPEN SYSTEMS alternative for Mainframe Sites planning on implementing the Client/Server concept in their overall IT-strategy. They are investing serious efforts in providing the solutions for those customers. One of the proofs is the tightened partnership with Software AG. Their Client/Servers applications have been ported to the HP 3000 (in 6 weeks). These products provides the request services in the Client/server environment to achieve transparent access to an enterprise's entire computer resources. HP has 4GL's to support the move of VM-applications. They want to off-load VM and put the end-user environment on a Corporate Business Server. Another partnership to support HP's strategy is HP's implementation of NetBase. NetBase provides a solution were servers can be clustered like a VAX-cluster, using 802.3 LAN or any HP NS link. HP has also tightened the partnership with Storagetek, starting to resell the 42XX 3480-compatible tapestations. Support for the Storagetek 42XX is provided by both HP 3000 and HP 9000. HP also plans to market tape-silos from Storagetek. In the end of the presentation, HP told about a marketing survey, they had ordered from Gartner Group. Based on the 1990 IBM installation base HP claimed, that HP's large systems are more powerful than over 90 percent of installed IBM mainframes. HP stated, that they were not aiming at replacing mainframes overnight, they preferred to be the cost-effective alternative for new applications, but were confident that the traditional mainframe thereby would suffer a slow death over the next ten years. The Corporate Business Servers are all very aggressively priced, regarding to TPC-A tps/K at the same level as the midrange servers. In US prices a normal UNIX one-processor configuration would cost about 450.000 USD. A 4-way about 950.000 USD. ************************************************************************* For those of you, who have read so far, I'm sorry for spoiling your day. Really IBM CONFIDENTIAL HP is still just entering the Client/Server arena. And they lack advanced application products. For example their imaging-products are weak regarding enterprise-integration. They have only low-function CallPath-like products from third-parties. And their system-integration capabilities are still weak. Though they have a Project Management Division, it is very young and unexperienced. So, if you want to keep HP out of reach of your customer, it is time to start up long-term, strategic projects, utilising our broad suite of advanced applications. This could mean, that you have to call on business managers and top business executives and discuss the benefits of a competitive edge IT-strategy. Not easy, but worthwhile doing, before HP does exactly the same. ************************************************************************* These were my impressions and reflections of the first day attending the HP-Users Conference in Copenhagen. I have one and a half day more to go, and I will provide you with a full report early next week. Have a nice day ;-) Best regards Torben Olsen Program Manager Competitive Marketing Support Centre Copenhagen TOL at DKIBMVM2 ====================================================================== >(I)92191. 970 vs 560 performance in a commercial environment. Recently IBM UK have benchmarked the newly announced RISC System/6000 model 970 and the model 560. Both of these processors have the same clock speed of 50MHz, however the 970 has an increased Instruction Cache (from 8kb to 32kb) and a higher speed Microchannel bus. The performance increase experienced was greater than anticipated and shows how effective the new design is. All software and other hardware was identical between the 560 and the 970. The only differences were the new architectural changes. RESULTS At a specific response time of 3 seconds (end to end measurement), the 970 allowed 28.4% higher throughput. At the maximum throughput (the vertical graph of response time vs throughput the 970 allowed 23.9% higher throughput. Obviously this result was for a specific benchmark and the resulting gain will be application dependant. CONFIGURATION The benchmark is a simulation of a suite of real customer applications. 560/970 acts purely as a database server with the applications running on 320H front end systems and running Ingres Client/Server. In this benchmark 7 320H systems were used to generate the workload as Ingres clients, and either the 560 or the 970 was used as the database server. The application is a help desk management system, configuration management problem reporting and change management system for 80+ mainframe computers (mainly ICL) and a growing number of UNIX servers/PC' (of mixed pedigree). In total the system is sized for 350 concurrent users. The benchmark system uses 15GB of 9333 serial disks to provide the database services and whilst I/O is heavy, the system is still CPU constrained. Software is AIX 3.2.1 on the server with Ingres 6.4.01.01. Software on the front end is AIX 3.1.5 with Ingres 6.4 Robert Ryan, ITSC - Austin May 22, 1992 ====================================================================== >(I)92192. GETTING STARTED WITH OPEN SYSTEMS A number of excellent sources of information provide an introduction as well as on-going updates to the open systems marketplace. The following documents on MKTTOOLS are good reference material: OPENPACK (Presentation) A comprehensive scripted presentation describing the elements of IBM's open systems strategy. OPENPROD A document listing some of the key industry, national and international standards and the IBM or IBM Cooperative Software products (if any) that implement them in the AIX and SAA environments. OPENRES A guide pointing to other resources for marketing and learning about open systems, including contact names and numbers. OPENORGS, COSTA, OPENTIME Three small documents that cover standards, consortia, standards groups, etc. While there is a large amount of overlap, the information organization and structure of each is different. To get any of the above documents, enter the following command: TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET nnnnnnnn PACKAGE where nnnnnnnn is one of the above names. To keep current with the latest developments in open systems, subscribe to the following: OPENSMKT FORUM (On IBMPC) A forum for informal information interchange among IBMers in the field and labs. Once you subscribe, you automatically receive new postings. If you are unfamiliar with FORUMS execute the following commands: TOOLS SENDTO YKTVMV IBMPC IBMPC GET OPENSMKT FORUM TOOLS SENDTO YKTVMV IBMPC IBMPC SUBSCRIBE OPENSMKT FORUM Paul Lugo - ITSC Austin May 26, 1992 ====================================================================== >(I)92193. NEW AIX INFORMATION ON HONE ASKQ (SETI) May 27, 1992 Have you seen the latest AIX Technical Information on HONE ASKQ? In April 1992, 3 Flashes and 12 HOWTO AIX items were added by AIX Systems Support and other support groups to assist you in closing and implementing AIX business. This information is now available through HONE with the command "ASKQ". The HOWTO AIX items are organized into groups. Each group is associated with a specific subject area. By searching a list of Q&A items using the keywords "HOWTO AIX", a list of all the HOWTO AIX items can be retrieved. If you have additional technical information needs that you would like us to address, please send your comments and suggestions to the PROFS ID: DALVM41B(HOWTOS) Flashes last month: Number Item title ======= ==================================================== G010327 DSSC FLASH 2090 X3270 RELEASE 1, REFRESH 2 G010314 DSSC FLASH 2077 AIX VERSION 3.2 FOR THE RISC SYSTEM/6000 TECHNICAL OVERVIEW AND G010312 DSSC FLASH 2070 3.2 MKSYSBACK UPGRADE UTILITY MUST BE MODIFIED BEFORE MAKING MULT VOLUME 1/4" BACKUP TAPES HOWTO's last month: Number Date Item title ======= ====== ================================================= Q587303 920424 HOWTO AIX: USE XDE ON AIX/ESA Q587304 920424 HOWTO AIX: IMPLEMENT SENDMAIL ON AIX/ESA Q585611 920413 HOWTO AIX: CHANGE A USERS HOME DIRECTORY Q585610 920413 HOWTO AIX: RUN XRTM AS A NORMAL USER (NOT ROOT) Q587307 920424 HOWTO AIX: ETHERNET 10BASET NETWORKING OVERVIEW Q587305 920427 HOWTO AIX: SET-UP A DISKLESS SERVER WHICH HAS MORE THAN ONE NETWORK ADAPTER. Q584421 920403 HOWTO AIX: REDUCE THE SIZE OF THE /USR FILESYSTEM IN AIX 3.2 Q584420 920403 HOWTO AIX: GET PAGE UP OR PAGE DOWN FUNCTIONALITY IN SMIT WHEN USING THE 3151 ASCII TERMINAL. Q586349 920417 HOWTO AIX: DETERMINE THE DIFFERENCES BETWEEN AIX WINDOWS 1.2 BASE AND AIXWINDOWS 1.2 3D, SOFTWARE AND HARDWARE. Q586350 920417 HOWTO AIX: PORTING GL APPLICATIONS TO THE GT4 AND GT4X ADAPTERS. Q587306 920424 HOWTO AIX: AIXWINDOWS ENVIRONMENT/6000 1.2 3D GRAPHIGS FEATURE, ENHANCEMENTS AND PORTING CONSIDERATIONS. Q585612 920413 HOWTO AIX: HOW TO GET COMPILED APPLICATIONS TO LOOK THE SAME AS WHEN CREATED INTERACTIVELY WITH AIC. ====================== End of Items ================================ Send questions related to this entry to DALVM41B(HOWTOS). ====================================================================== >(I)92194. LOTUS TO SHIP VERSION 1.2 OF LOTUS 1-2-3 FOR THE /6000 Lotus Development Corp. announced May 26, 1992 Version 1.2 of Lotus 1-2-3 for the IBM RISC System/6000. This version of the world's most popular spreadsheet has all the features of 1-2-3 Release 3.0 for DOS as well as enhancements for the UNIX environment and a Motif Interface. This is the real 1-2-3, the spreadsheet of choice for over 16 million users, complete with a 3 dimensional worksheets, over 100 functions, relational database, presentation graphics, macro programming, and the file linking. 1-2-3 for the RS/6000 also includes the C Add-in Toolkit for developing custom functions or interfaces between 1-2-3 and other programs, and DataLens, which enables customers to use 1-2-3 as a front end to external databases. Drivers for Informix and Sybase databases are included. Lotus 1-2-3 for the IBM RISC System/6000 version 1.2 is fully compatible with all releases of Lotus 1-2-3, including those on DOS, Windows, OS/2, and IBM mainframes. Lotus 1-2-3 for the IBM RISC System/6000 will ship in June, The product will be sold through Lotus' national distributors, including Ingram Micro, Merisel, and Dickens Data. 1-2-3 for the RS/6000 has a retail price of $695 for server and workstation use. Add-on nodes for character terminal users are available for a suggested retail price of $295 each, $1,250 for a 5 pack, or 4,525 for a 25 pack. Version 1.2 of Lotus 1-2-3 for the IBM RISC System/6000 runs on IBM POWERstations and POWERservers with AIX 3.1.5 and greater, Motif 1.1, 10MB of RAM in character (TTY) mode and 16MB for the Motif Interface. A minimum of 15MB of disk space is required. Questions on this notice are to be forwarded to: RHQVM21(KROBERTS). # # # # # All prices and terms are for the U.S.A. only. Lotus 1-2-3, and DataLens are registered trademarks of Lotus Development Corporation. UNIX is a registered trademark of UNIX System Laboratories, Inc. Motif is a registered trademark of the Open Software Foundation. Informix is a registered trademark of Informex Software, Inc. Sybase is a registered trademark of Sybase, Inc. Windows is a trademark of Microsoft Corporation, TBM, AIX and OS/2 are registered trademarks, and RISC System/6000 are trademarks of International Business Machines Corporation. Classic is a registered trademark licensed to Lotus Development Corporation. ====================================================================== >(I)92195. GRAPHICS SYSTEMS CUSTOMER SATISFACTION SURVEY May 26, 1992 On May 20 and May 21 a note was sent to 517 marketing people covering most branch offices asking for names of customers who would be willing to participate in a Customer Satisfaction Survey for Graphics Systems. As of May 26 only 35 nominations have been received. Please, if you know of a customer using one or more of the five listed Graphics Systems products, send nominations (along with the Graphics product being used) to KGNVMY(BLACKER). As part of an on-going effort to improve our products and your customer's level of satisfaction, Graphics Systems development in AWD is planning to conduct a survey in June to sample CUSTOMER SATISFACTION with certain Graphics products - 6091-19...........Graphics Display 5086..............Graphics Control Unit GtO...............7235 POWERgraphics adapter gl................Graphical User Interface / Graphics Library graPHIGS..........Graphics User Interface If you think your customer(s) could/would participate in a short telephone survey, please respond and send us the person's name(s), (more than one is fine), company name, and day-time phone number. We're looking for end-users, decision makers, system administrators, designers, engineers,........someone with direct experience with one or more of the products. We need the names and numbers as soon as possible (before the end of May). It would also be useful to indicate which of the five Graphics products they're using. Your help in providing us with a direct contact is appreciated. We're also interested in any comments you have. If the account assignments have changed and you no longer deal with Graphics customers, please forward this note to someone who does. Thanks much,...........Bob Blacker KGNVMY (BLACKER) Questions on this notice are to be forwarded to KGNVMY(BLACKER). ====================================================================== >(I)92196. AIX VERSION 3.2 PERFORMANCE MEASUREMENTS FINAL REPORT May 28, 1992 This document reports the performance of selected hardware and software elements of AIX 3.2 running on the RISC System/6000 platform. Included are sections on SPEC1.2, Linpack, Livermore Loops, Disk, NFS, TCP/IP and Netware. The measurements were performed by the AIX Programming Center in Austin, TX., and are classified IBM Internal Use Only. To receive a copy of the report, enter the following command from your VM account: TOOLS SENDTO DALVM41B TOOLS AIXIC GET PERF-3_2 PACKAGE You will receive a package description file and a LIST3820 file that can be printed with your favorite print utility. Questions on this notice are to be forwarded to: DALVM41B(HEISE) ====================================================================== >(I)92197. AIX CASE PRODUCTS AVAILABLE, ON SCHEDULE May 29, 1992 The IBM Computer-Aided Software Engineering (CASE) tools, designed to enhance software development in the AIX(R) RISC System/6000 operating environment, begin shipment on schedule May 29. These products, announced on January 21, 1992, include the following: 5696-037 IBM AIX Software Development Environment WorkBench/6000 5696-137 IBM AIX Software Development Environment Integrator/6000 5765-039 IBM AIX Configuration Mgmt. Version Control Server/6000 5765-069 IBM AIX Configuration Mgmt. Version Control Client/6000 5765-037 IBM AIX MVS Library Connector/6000 5695-121 IBM Library Connector for AIX/MVS 5765-035 IBM AIX XL C++ Compiler/6000 Along with the XL C, XL FORTRAN, COBOL, PASCAL and Ada compilers, software development on the RISC System 6000 is at a world class level. Approximately 1/3 of all RISC Systems installed are used for software development. Take your customer for a test drive today and feel the POWER| Marketing deliverables (i.e. Presentation Guide, Marketing Guide, etc.,) are available on the Marketing Tools disk. To request these IBM Internal Use Use Only marketing deliverables, enter the following command from OV/VM: : TOOLCAT MKTTOOLS GET AIXCASE PACKAGE If TOOLCAT is not installed on your system, type the following: TOOLS SENDTO BCRVMMS1 TOOLS MKTTOOLS GET AIXCASE PACKAGE For more information regarding these products, contact the AIX CASE Support Center at tieline 752-7386, or DFWVM04(CASE). These products are described in Announcement # 292-011, IBM AIX CASE SOFTWARE DEVELOPMENT SOLUTIONS OVERVIEW, dated January 21, 1992. ====================================================================== >(I)92198. IBM ANNOUNCES THE 3270 EMULATOR FOR THE X WINDOW SYSTEM June 2, 1992 The IBM 3270 Emulator for the X Window System (x3270) Release 2, combines new function and multi-platform support in a single x3270 product. Customers looking for an Open Systems Solution for connectivity between UNIX workstations and IBM S/370 and S/390 over TCP/IP now have even greater capability. x3270 Release 2 builds on the primary advantages of x3270 over alternative 3270 emulation solutions (support for GDDM graphics, APL2 characters, extended data stream, cut and paste), while adding new functions to increase flexibility in the customer environment, and promote enterprise-wide usage of the product. NEW RELEASE 2 FUNCTIONS INCLUDE: * RESIZABLE GRAPHICS and Non-graphics Sessions * Interactive Graphical Keyboard Remapper * xHLLAPI Support * Enhanced Mouse Functionality - xButtons - autoAction - autoPrepend - X.desktop Support - Light Pen Support * National Language Support (SBCS) * NetLS 2.0 Support (License Server on OEM hardware) NEW PLATFORM ANNOUNCED: x3270 is available as a Program Product for RISC System/6000, Sun-4, and Hewlett Packard workstations. Program Number: 5765-011 Brochures can be ordered through PUBORDER. Pub Number: G521-1215-00. FREE 30 Day demo copies are available to customers upon request. Contact: Kathy Lange at t/l 695-5527 or KLANGE at KGNVMA. ====================================================================== >(I)92199. Sparcstation 10 Last week Sun Microsystems announced their new family of SPARC based workstations based on the newly announced processors from Texas Instruments. By this announcement Sun Microsystems is (again) targeting the full range workstation range from the low end ELC (newly re-priced at base USD: 3.995,-) to the top, the Sparcstation 10. By this LONG append I have tried to summarize the information available and to give some hints to the future marketing from IBM. Since everybody has been talking about the new Sparcstation 3 the new products from Sun are named Sparcstation 10 (just to fool the masses). The announcement consists of four models based on different CPUs operating at various clock-speeds. Sparcstation 10 Model 30 Model 41 Model 52 Model 54 No. of Processors 1 1 2 4 Cache 36k inter- 1 MB exter- 1 MB exter- 1 MB exter- nal cache nal cache nal cache nal cache MHz 36 40 45 45 SPECint92 44.2 52.6 SPECfp92 52.9 64.7 SPECthruput89 (est.) 109 218 MIPS 86.1 96.2 200+ 400+ Price $18,495 $24,995 $39,995 $57,995 Availability Q3-92 Q3-92 Q4-92 Q1-93 OS required S 1.1 S 1.1 S 2.0 S 2.0 NFS ops./sec. 700+ 800+ tps (est.) 100 120 180 220 All models include ISDN connectivity, microphone and CD (16 bit) audio for multi-media. Four SBus slots are available. Up to 26 GB of storage and up to 512 MB internal memory. All model are upgradeable by switch of the processor-board to either MP configurations or to higher processor speed when available from Texas Instruments According to Sun all programs running on older SPARC systems will run on the SS10. Binary compatibility is offered throughput the whole range of systems. On the other hand the SPARC implementation in the SS10 is widely different from the earlier SPARCs. The bus-speed has doubled and and the memory speed quadrupled. ************************************************************************* To compare with the IBM performance figures: Note that the SPEC-92 figures can not be compared to the old SPEC figures. For currently available models: Model 220 320H 340 350 520H 530H 550 560 950 970 SPECint92 15.9 20.9 27.7 34.6 20.9 28.2 35.4 42.0 35.4 47.1 SPECfp92 22.9 39.4 51.9 65.0 39.6 57.6 71.7 85.5 71.7 93.6 ************************************************************************* And about price / performance: ---------------------------------------------------------- | | Sun | Sun | Sun | Sun | | Metric | SS10/M30 | SS10/M41 | SS10/M52 | SS10/M54 | |---------------------------------------------|----------| | US List * | $ 18,495 | $ 24,995 | $ 39,995 | $ 57,995 | | engine | $ 11,500 | $ 18,000 | | | | only | | | | | |--------------------------------------------------------- |$/SPECint92 | $ 464 | $ 513 | | | |$/SPECfp92 | $ 388 | $ 417 | | | | $/MIPS | $ 238 | $ 281 | $ 200 | $ 145 | | $/Mflops | $1,934 | $1,569 | $1,053 | $ 763 | | $MB/RAM | $ 81 | $ 81 | $ 81 | $ 81 | | $MB/Disk | $ 4.48 | $ 4.48 | $ 4.48 | $4.48 | ---------------------------------------------------------- Note *: Standard configurations with 19" accelerated color, 32MB, 400MB disks except for SS10/52 & 54 (64MB, 1GB) ************************************************************************* CMSC Comment: ************* By this announcement SUN is aggressively going for the middle and high end of the workstation arena. The Sparcstation 10 is positioned against the IBM 3xx and 5xx, the HP 720, 730 and 750 and against the SG Crimson based on the MIPS R4000. Based on the above figures the SPARCstation 10 offers a very competitive price/performance ratio. However the are some focal points for the future IBM marketing: First of all the machines are not available NOW. So push the sales. Try to convince the costumer that he need to get his hands on the system and make an on site benchmark. This will give you some time. Only the single CPU systems are available this year. Secondly (and once again) we must stress the report (available on COMP on HONE) from D.H. Brown comparing SunOS (or Solaris 1.0) to IBM AIX 3.2 (and several other UNIXies). The AIX operating system is a winner| Thirdly the full binary compatibility of the SPARC 10 has yet to be proven. And to use the MP in the 50 models you must run Solaris 2.0 and them we're talking migration. The Solaris 1.1 is mainly BSD and some USL V.3. The Solaris 2.0 will be fully USL V.4 with Sun enhancements. Further more how well can a workstation user use several CPU's on his desk? I would question that| Finally there is the performance issue. IBM is still by far the leader in floating point performance. The 350, the 550 and 560 and the 950 and 970 all offers higher FP figures than Sun. We do have an edge here. The very large cache offered on the Sun systems of course gives them a high rating in SPEC benchmarks but how about some real life results from heavy technical computing. Good luck in the Risc System/6000 marketing. **************************************************************** * Best regards, * * Klavs Frisdahl * * Program Manager, UNIX Technical Workstation * * Competitive Marketing Support Center, Copenhagen, Denmark * * * * IBM: FRISDAHL at DKIBMVM2 * * Internet: frisdahl@dkibmvm2.vnet.ibm.com * * Telephone: + 45 45 93 45 45, FAX: + 45 43 43 05 10 * **************************************************************** ====================================================================== >(U)92200. AIX 3.2 crontab security vulnerability =========================================================================== CA-92:10 CERT Advisory May 26, 1992 AIX crontab Vulnerability --------------------------------------------------------------------------- The Computer Emergency Response Team/Coordination Center (CERT/CC) has received information concerning a vulnerability in crontab(1) in version 3.2 of IBM's AIX operating system. IBM is aware of this problem and a fix is available as apar number "ix26997" for AIX version 3.2. The version information for the patched /usr/bin/crontab is shown in the following what(1) output: % what /usr/bin/crontab 04 1.23 com/cmd/cntl/cron/crontab.c, cmdcntl, bos320, 9218320f 4/8/92 11:50:42 07 1.8 com/cmd/cntl/cron/permit.c, bos, bos320 4/25/91 17:16:59 11 1.15 com/cmd/cntl/cron/cronsub.c, bos, bos320 8/18/91 20:42:32 06 1.9 com/cmd/cntl/cron/funcs.c, bos, bos320 6/8/91 21:22:40 If your crontab contains older modules than the above output indicates, we suggest that you install the fix. --------------------------------------------------------------------------- I. Description The distributed version of /usr/bin/crontab contains a security vulnerability. II. Impact Local users can gain unauthorized root access to the system. III. Solution The CERT/CC suggests that sites install the fix that IBM has made available. As an interim step, we suggests that sites prevent all non-root users from running /usr/bin/crontab by removing (or renaming) the /var/adm/cron/cron.allow and /var/adm/cron/cron.deny files. - Obtain the fix from IBM Support. 1. To order from IBM call 1-800-237-5511 and ask that the fix be shipped. Patches may be obtained outside the U.S. by contacting your local IBM representative. 2. If you are on the Internet, use anonymous ftp to obtain the fix from software.watson.ibm.com (129.34.139.5). Patch Filename Checksum AIX 3.2 pub/aix3/cronta.tar.Z 02324 154 The patch must be retrieved using binary mode. - Install the fix following the instructions in the README file. --------------------------------------------------------------------------- The CERT/CC would like to thank Fuat Baran of Advanced Network & Services, Inc. for bringing this security vulnerability to our attention and IBM for their quick response to this problem. --------------------------------------------------------------------------- If you believe that your system has been compromised, contact CERT/CC or your representative in FIRST (Forum of Incident Response and Security Teams). Internet E-mail: certcert.org Telephone: 412-268-7090 (24-hour hotline) CERT/CC personnel answer 7:30 a.m.-6:00 p.m. EST(GMT-5)/EDT(GMT-4), on call for emergencies during other hours. Computer Emergency Response Team/Coordination Center (CERT/CC) Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Past advisories, information about FIRST representatives, and other information related to computer security are available for anonymous ftp from cert.org (192.88.209.5). ====================================================================== >(U)92201. Shrinking the /usr filesystem on 3.2 From: lennyicus.ICUS.COM (Lenny Tropiano) Newsgroups: comp.unix.aix In article <1992May22.031709.25490ncar.ucar.edu> fredrickacd.acd.ucar.edu (Timothy Fredrick) writes: >The directions in the FAQ that I have didn't help. Briefly, it said to Those directions are specific to AIX 3.1.x and will not work on 3.2 >The problem is that umount won't allow you to unmount /, /tmp, or /usr. I That's right. The "getrootfs" script does a mount -f /dev/hd4 /, instead of mounting it as "/mnt". The big reason was the reorganization of the filesystem. With 99.9% of the binaries being in the /usr/bin, /usr/sbin, and other /usr directories, you cannot easily strink /usr (without all the commands that are in /usr, no longer in /etc or /bin (only symlinks exist now). It was deemed easier and faster, to do a: # cd / # mkszfile # vi /.fs.size Edit the /usr LP's that it will make. # mksysb /dev/rmt0 Then reinstall the AIX 3.2 system with the new mksysb tape. BTW: The tape is now bootable too. ====================================================================== >(I)92202. AIX 3.1 to AIX 3.2 Upgrade Tools Package for RS/6000 The upgrade tools are now available on a tools disk at munivm4. You will find a package of tools for upgrading from AIX 3.1 to AIX 3.2. It consists of the standard upgrade tools, the Upgrade Redbook, the "turbo tools" for systems with external disks and some documentation about the "turbo tools". Request the package with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET UPGTOOLS PACKAGE or TOOLS SENDTO DALVM41B IBMPC AIXDOC GET UPGTOOLS PACKAGE from your VM id. If you have no tools command, check with your IS people. What you get: UPGTOOLS README * README file UPGTOOLS BAKBIN * Standard Upgrade Tools, binary backup file, download it BINARY and use dd command to generate diskette in backup format or restore directly out of the binary file UPGTOOLS TRSL3820 * Redbook "Upgrading to AIX 3.2, the inside story", un-terse it and print as LIST3820 file, shows how to use the standard tools TURTOOLS BAKBIN * "Turbo tools" for systems with external disks, binary backup file, download it BINARY and use dd command to generate diskette in backup format or restore directly out of the binary file TURTOOLS TRSL3820 * Documentation about the "turbo tools", un-terse it and print as LIST3820 file, shows how to use the "turbo tools" Have fun and many upgrades. Andreas Hermelink VM: HERMELI at MUNIVM4 06.02.92 Internet: hermelibm.de ====================================================================== >(I)92203. XDM package of configuration files I put a package of nifty configuration files for XDM, with a few READMEs, and other things that should get a decent XDM configuration going. I also document how to fix the current AIX 3.2 XDM bug, and provide sample .xsession and other scripts. It is a compressed tar file, which goes into /usr/lib/X11/xdm directory. Mickey Coggins mcog at chvm1 get it via TOOLCAT AIX ====================================================================== >(U)92204. WIT - What Is This A nice way to list your machine type and configuration: #|/bin/sh #(#) wit Version 1.1 26-May-92 # # Date: Tuesday; May 26, 1992 09:20:24 EDT # # Disclaimers: I do not guarantee anything about this shell script; # you are officially "yoyo" (You'reOnYourOwn). # # Program Name: WIT (as in; WhatIsThis) # # Author: D. R. Ranz; IBM Corporation, Detroit, Michigan # # Inspiration: This shell script was inspired by several FORA postings. # It is not my intention to ignore those authors - but # their respective postings did not note authorship and # I no longer recall the names of those that contributed. # # Purpose: To provide a salient summary of the system configuration # and performance. # # Random # Thought: NEBA is (almost) ABENd spelled backwards. # # 28-May-92: Jason Behm provided a tip to distinguish between the # 530 and 730. # # Corrected the 970 Machine type; it should be "63" # # Added memory bus performance information for the 530H # # Altered the catchall clause to echo the machine type # that was unknown. # if test "$TERM" |= dumb0 then tput clear fi # UNIQ=`uname -m cut -c3-10` TYPE=`echo $UNIQ cut -c7-8` UNIQ=`echo $UNIQ cut -c1-6` STRING="IBM RISC System/6000nModel: " case $TYPE in "10") MODEL="530 or 730" if test `lscfg -v grep GEMINI wc -l` = 0 then MODEL="530" else MODEL="730" fi VERBOSE="25 MHz clockn64 KByte data cachen8 KByte instruction cachen15.4 MFL OPSn46.1 SPECmarksn1 Microchannel bus 40 MBytes/secn128-bit memory bus 400 MBytes/secn" ;; "11") MODEL="540" VERBOSE="30 MHz clockn64 KByte data cachen8 KByte instruction cachen16.5 MFL OPSn38.7 SPECmarksn1 Microchannel bus 40 MBytes/secn128-bit memory bus 480 MBytes/secn" ;; "14") MODEL="540" VERBOSE="30 MHz clockn64 KByte data cachen8 KByte instruction cachen16.5 MFL OPSn38.7 SPECmarksn1 Microchannel bus 40 MBytes/secn128-bit memory bus 480 MBytes/secn" ;; "18") MODEL="530H" VERBOSE="33 MHz clockn64 KByte data cachen8 KByte instruction cachen20.2 MFL OPSn59.9 SPECmarksn1 Microchannel bus 40 MBytes/secn128-bit memory bus 528 MBytes/secn" ;; "1C") MODEL="550" VERBOSE="41.7 MHz clockn64 KByte data cachen8 KByte instruction cachen23.0 M FLOPSn54.3 SPECmarksn1 Microchannel bus 40 MBytes/secn128-bit memory bus 66 7 MBytes/secn" ;; "20") MODEL="930" VERBOSE="25 MHz clockn64 KByte data cachen8 KByte instruction cachen15.4 MFL OPSn46.1 SPECmarksn1 Microchannel bus 40 MBytes/secn128-bit memory bus 400 MBytes/secn" ;; "2E") MODEL="950 or 950E" VERBOSE="41.7 MHz clockn64 KByte data cachen8 KByte instruction cachen25.2 M FLOPSn72.2 SPECmarksn1 Microchannel bus 40 MBytes/secn128-bit memory bus 66 7 MBytes/secn" ;; "30") MODEL="520" VERBOSE="20 MHz clockn32 KByte data cachen8 KByte instruction cachen9.2 MFLO PSn32.8 SPECmarksn1 Microchannel bus 40 MBytes/secn64-bit memory bus 160 MB ytes/secn" ;; "31") MODEL="320" VERBOSE="20 MHz clockn32 KByte data cachen8 KByte instruction cachen9.2 MFLO PSn32.8 SPECmarksn1 Microchannel bus 40 MBytes/secn64-bit memory bus 160 MB ytes/secn" ;; "35") MODEL="320H" VERBOSE="25 MHz clockn32 KByte data cachen8 KByte instruction cachen11.7 MFL OPSn43.3 SPECmarksn1 Microchannel bus 40 MBytes/secn64-bit memory bus 160 M Bytes/secn" ;; "37") MODEL="340" VERBOSE="33 MHz clockn32 KByte data cachen8 KByte instruction cachen14.8 MFL OPSn56.6 SPECmarksn1 Microchannel bus 40 MBytes/secn64-bit memory bus 264 M Bytes/secnIntegrated ethernetnIntegrated SCSI" ;; "38") MODEL="350" VERBOSE="41.7 MHz clockn32 KByte data cachen8 KByte instruction cachen18.6 M FLOPSn71.4 SPECmarksn1 Microchannel bus 40 MBytes/secn64-bit memory bus 333 MBytes/secnIntegrated ethernetnIntegrated SCSI" ;; "41") MODEL="220" VERBOSE="33 MHz clockn8 KByte data cachen0 KByte instruction cachen6.5 MFLOP Sn25.9 SPECmarksn1 Microchannel bus 40 MBytes/secn32-bit memory bus 89 MByt es/secnIntegrated ethernetnIntegrated SCSI" ;; "5C") MODEL="560" VERBOSE="50 MHz clockn64 KByte data cachen8 KByte instruction cachen30.5 MFL OPSn89.3 SPECmarksn1 Microchannel bus 40 MBytes/secn128-bit memory bus 800 MBytes/secn" ;; "63") MODEL="970" VERBOSE="50 MHz clockn64 KByte data cachen32 KByte instruction cachen30.7 MF LOPSn100.3 SPECmarksn2 Microchannel busses 80 MBytes/sec eachn128-bit memory bus 800 MBytes/secn" ;; *) MODEL="Error: This system type ("$TYPE") is unrecognized, please get th e latest edition of wit" esac echo $STRING $MODEL. echo "Hardware ID: $UNIQ" echo $VERBOSE lscfg -l mem* cut -c39-70 sed "s/^ *//" sed "s/ *$//" grep 0-9 echo "" lscfg -l hd* cut -c39-79 sed "s/^ *//" sed "s/ *$//" grep 0-9 echo "" lscfg -l rmt* cut -c39-79 sed "s/^ *//" sed "s/ *$//" grep 0-9 echo "" lscfg -l cd* cut -c39-79 sed "s/^ *//" sed "s/ *$//" grep 0-9 ====================================================================== >(U)92205. HOTW: Join two files using a relational-like lookup operation The JOIN command is a bit like a having an SQL-database-join operation ... without all the pain and $uffering of a RDBMS. The collation (sort) order of the 'key' field is very important. $cat names 313-436 9503 Doug Ranz, 313-552 5977 John Zachos, 614-225 3585 Carol Oswald, 614-225 3650 Rick, Beach, $cat phones.xref 313-436 Dearborn, Michigan 313-552 Southfield, Michigan 614-225 Columbus, Ohio $join names phones.xref 313-436 9503 Doug Ranz, Dearborn, Michigan 313-552 5977 John Zachos, Southfield, Michigan 614-225 3585 Carol Oswald, Columbus, Ohio 614-225 3650 Rick Beach, Columbus, Ohio There are many options for the join command. They permit you to specify output options, matched lines, unmatched lines, collation sequence, etc ... checkout the man page(s). Dough Ranz ====================================================================== ====================================================================== backward combatability: /bak'w*rd k*m-bat'*-bil'*-tee/ from `backward compatibility' n. A property of hardware or software revisions in which previous protocols, formats, and layouts are discarded in favor of `new and improved' protocols, formats, and layouts. Occurs usually when making the transition between major releases. When the change is so drastic that the old formats are not retained in the new version, it is said to be `backward combatable'. See flag day. >92.06.16 Table of contents: (U)92206. Crashes with Memory scrubbing on 340 and 350 (U)92207. Limiting the operation of find to local filesystems (I)92208. Noisy 340 and 350 systems (I)92209. Information about Diskless Support fixes: (I)92210. NEW COMPETITIVE MODULES ON COMP/HONE (I)92211. Wang to RISC System/6000 Migration Presentation (U)92212. Reducing the primary paging space on AIX 3.2 (I)92213. AIX VERSION 3.2 FOR RISC SYSTEM/6000 SOURCE CODE AVAILABILITY (I)92214. TCP/IP MVS 2.2 - NEW RELEASE SUPPORTS CICS (I)92215. 3172 MODEL 3 (WITH TCP/IP OFFLOAD), MOD 2 ENHANCEMENTS, AND ICP V3 (I)92216. IBMs commitment to OSF (U)92217. How do I see what processes are killed when out of paging space? (U)92218. Mwm color definitions on mono screens (U)92219. HOTW: How do you log all your actions in the shell? ====================================================================== >(U)92206. Crashes with Memory scrubbing on 340 and 350 I've read about 2 different people with crashes they believe to be related to memory scrubbing, one 340 and one 350. It turns out there *IS* a defect related to memory scrubbing. The numbers are: APAR number - IX27144 PTF number - U403579 Until you get these fixes, do: chdev -l sys0 -a memscrub=false Mickey Coggins ====================================================================== >(U)92207. Limiting the operation of find to local filesystems In AIX 3.1.x, the option is the -prune as has been suggested. This option prevents the traversal of remote filesystems. In AIX 3.2, the -prune option prevents the traversal of subdirectories. What you want to use in this release, is the -fstype option. This option allows only the filesystem specified to be traversed (you can of course use the -o conjunction to allow other filesystem types). Or you might want to try out the -xdev option which prevents the traversal of filesystems different that the one specified (indirectly) by the PATH specified. arnold ====================================================================== >(I)92208. Noisy 340 and 350 systems There was some discussion last month on noise emanating from the keyboard speaker of the 340 and 350 systems. The noise is enhanced by heavy system activity causing inductive noise to be coupled into the analog amplifier circuitry from nearby high speed digital lines on the I/O planar board. The level of noise is application dependent (ie CPU intensive applications will cause higher noise levels at higher frequencies), so you may not even notice a problem with a machine that idles most of the time or if the machine is in a noisy environment. Austin has made a fix to the analog circuitry to suppress this noise which is scheduled to be broken into manufacturing this week. The new planar part number is 51G8631 (IEC 12604763) and will shortly be available to the field. John Woo '6000 Product Engineering ====================================================================== >(I)92209. Information about Diskless Support fixes: There have been 2 Preventative Maintenance Packages (PMP) for diskless : one was shipped with the 3.2.1 Selective Enhancement (SE), and the second will be shipped with the next SE soon to be released. It is anticipated that there will be more fixes that will be shipped with future SEs. Each of these PMPs contain Program Temporary Fixes (PTFs) which fix problems that have had defects for, which include problems found in DWM as well as NFS, TCPIP, bosboot, and install. The latest PMP will always have as a prerequisite the previous ones, so you only have to order the latest PMP and you will get all the previous ones required. The latest PMP is PTF # U403380. If you don't already have this fixes, it is strongly recommended that you get the latest one and apply it to your server. When installing these fixes, it is recommended that you use SMIT, and that you descend the SMIT menu tree starting from Diskless Workstation Management; this will allow you to install these fixes into all of your SPOTs and diskless clients. When you get to the screen "Install Software with Updates" screen, use F4 on the "SOFTWARE to install" field in order to display your choices; from this list, just select U403380, and all of the fixes will be installed. This will allow you to avoid having to select each one. ***** Warning : "installp" is used to install all AIX software (including fixes). When it attempts to install a fix for itself, it will stop and print a message. You will then have to restart the installation. ****** ====================================================================== >(I)92210. NEW COMPETITIVE MODULES ON COMP/HONE June 12, 1992 Strategy and Comparison documents comparing the RISC System/6000 to the Competition have been updated as of 6/2/91. These updates reflect recent IBM/Competitive price changes and recent competitive announcements ex. SUN SPARCstation 10. A new type of competitive paper has been added: Competitive Snapshot It's fast reading, informative and to the point. It's great for a sales call. First one is called: DECSTATION 5000: Competitive Snapshot Fastest way to find all RISC System/6000 competitive modules is to type BRO on source line of COMP/HONE screen Contact AArtale at RHQVM05 ====================================================================== >(I)92211. Wang to RISC System/6000 Migration Presentation I recently gave a presentation to a large Wang customer concerning a POTENTIAL migration strategy from Wang to RISC/6000. Since this may be of use to someone else, I am making it available via REQUEST. The foils were produced using Freelance for OS/2. An abstract follows..... * The presentation is aimed mainly at a large Wang shop. The strategy * * presented is to migrate the customer's Wang install base to a * * client/server architecture based upon open protocols and I position * * the RISC System/6000 and AIX as the ideal platform to achieve this. * * Because the original presentation was made to a customer who was * * largely ignorant of Open Systems, a fair number of the foils * * describe Open Systems. * To get this presentation, issue the following command from your CMS command line: REQUEST WANG-RS FROM SGRANT AT VANVM3 stephen grant ====================================================================== >(U)92212. Reducing the primary paging space on AIX 3.2 In case others are wondering, I'll answer my own append. Most of the following is from Paul Roberts and Tom Prokop. (Thanks, guys.) The method is different than the 3.1.x method. the swap-on command is run in 2 places in 3.2 during boot. look in /etc/rc for: # Activate all paging spaces in automatic list # (those listed in /etc/swapspaces) dspmsg rc.cat 3 ' Activating all paging spaces \n' /etc/swapon -a and in /sbin/rc.boot for: # Start paging swapon /dev/hd6 To change the default paging device, a good idea for performance/size reasons, do the following: -Create a new paging space. You may want to make it activated at IPL. -Edit the line in /sbin/rc.boot that activates /dev/hd6, either comment it out or change /dev/hd6 to your new page space. (I did the latter which caused the system to come up alright, but an "lsps -a" said that neither page space was active!) -De-activate hd6 at IPL, again via SMIT or chps -a -n hd6. -Rebuild the boot logical volume image with bossboot -d/dev/hdisk# -a where # is the boot disk you are using. -Shutdown the system, shutdown -rF. Be sure to wait until the bosboot command completes successfully, or you will be hosed :-{ -Remove the old hd6 page space with rmps hd6 command. I've heard that the /dev/hd6 page space is needed for "warm" installs so I also did the following: - Create another page space. This will probably have a minor device number of 1, which is what /dev/hd6 used to be. - Run chlv -n hd6 pagingXX where "pagingXX" is the name of your new page space. This will change it's name to "hd6". - Change the "swapon" command in /sbin/rc.boot back to the way it was. - Rerun "bosboot". Finally, the most important thing of all ... - Don't ever again increase the size of the primary page space. :-) Jack Goldstein ====================================================================== >(I)92213. AIX VERSION 3.2 FOR RISC SYSTEM/6000 SOURCE CODE AVAILABILITY June 16, 1992 AIX Version 3.2 for RISC System/6000 Source Code is now available, as announced today, as PRPQ P91084 on HONE. This is a Non-Standard, I-Listed PRPQ requiring Lab approval prior to ordering. It is intended for customers with requirements for Source Code for their own internal business purposes, and who have the requisite, self-sufficient, technical expertise to use the Source Code effectively. In addition to the PRPQ description, a Question and Answer package is available electronically to assist in your marketing positioning and strategy. To request the Q's and A's, formatted as a LIST3820 file, key the following on your PROFS command line: TOOLS SENDTO DALVM41B TOOLS AIXIC GET SOURCEQA PACKAGE Questions regarding this notice should be forwarded to: AUSVM6 (AIXSRC) For IBM "internal use" of the Source Code, two additional packages are available to explain the terms, conditions and requirements. Prior to requesting this PRPQ, be certain to request and read these items: TOOLS SENDTO DALVM41B TOOLS AIXIC GET SRC-INFO PACKAGE This package is intended for IBM "INTERNAL USE ONLY" and provides a brief description of the PRPQ, ordering and licensing information and a Certification form to be completed and returned. NOTE: YOU ARE PROHIBITED FROM REDISTRIBUTING THIS SOURCE CODE FOR REDISTRIBUTION INFORMATION REQUEST PACKAGE BELOW. TOOLS SENDTO DALVM41B TOOLS AIXIC GET SRC-DIST PACKAGE This package is intended for IBM "INTERNAL USE ONLY" and provides a brief description of the PRPQ. It also provides a questionnaire to be completed and returned to Development Relations Department (DEVRELS) prior to receiving redistribution rights authorization. Questions regarding these two packages should be forwarded to: AUSVMQ(DEVRELS) ====================================================================== >(I)92214. TCP/IP MVS 2.2 - NEW RELEASE SUPPORTS CICS June 16, 1992 A new release of TCP/IP for MVS has been announced and will be available on June 26, 1992. Two new features, CICS Socket Feature and Offload for OS/2 Feature, will be available on September 25,1992. New and enhanced features: CICS Sockets Support for Client/Server applications MVS Offload using new 3172 Model 3 Print support using LPR/LPD REXEC Client / Kerberos / NCS Network Database support (NDB) FTP batch SQL Query support SMF support for TELNET AND FTP RISC/6000 Channel Attachment Host Channel to Channel, CETI, and HIPPI Announcement material for MVS TCP/IP V2.2 The MVSTCP22 MKTTOOLS package includes ALL announcement material for TCP/IP MVS 2.2. Several of the files in the package will be permanently available in other package files. The TCPMVS22 package will be available for about 6 months. The permanent MKTTOOLS packages file are: TCPMVS, TCPNEWS, TCPCOMP. If you get MVSTCP22 then you do not need to request the other packages. CONTENTS: 1. TCPMVSPR - Press Release 2. TCPCOMP - Review of competitive TCP/IP solutions taken from publicly available sources. (Also available in TCPCOMP package). 3. TCPMVSQA - General Q&A package for MVS 2.2 4. TCPNEWS04 - TCP/IP Newsletter #4 - June 16,1992 edition (Also available in TCPNEWS). In addition, a presentation guide describing TCP/IP Version 2.2 for MVS is contained in this TCPMVS22 MKTTOOLS package. An updated TCPMVS package file will contain only the presentation material without the rest of the announcement package. The package consists of 5 sets of tersed files that must be unpacked into LIST3820 files and separate script files. TCPMVSOV Charts = 6, Print =10 min., Overview TCPMVSCS Charts =13, Print =30 min., Application section TCPMVSNC Charts = 7, Print =20 min., Connectivity TCPMVSUM Charts = 4, Print =10 min., Summary charts TCPMVSB1 Charts = 8, Print =25 min., Relationship to NS Blueprint In addition to these packages a softcopy proposal insert is also available --G221-2991-01. FTN TCP-V2.2, 3172, and Directions July 10 This one hour Field Television Broadcast will review the recent announcements and present IBM's Trends and Directions for TCP/IP on the host and workstation platforms. Broadcast receive facilities are in all IBM branch office locations and are available for direct customer receipt with satellite receive capability. The broadcast will be at 9:30AM EDT and repeated at 12:30 EDT for West Coast reception. For more information contact: Alan Reinhold 919-301-3173 8/352-3173 ====================================================================== >(I)92215. 3172 MODEL 3 (WITH TCP/IP OFFLOAD), MOD 2 ENHANCEMENTS, AND ICP V3 June 16, 1992 IBM announces the 3172 Interconnect Controller Model 3 LAN gateway - for sending information from Token-Ring, Ethernet, and FDDI Local Area Networks to mainframes. When used with the new TCP/IP for MVS offload application, announced today, the Model 3 can reduce host TCP/IP cycles. With TCP/IP offload, some of the TCP/IP work is handled by a 3172-003 instead of a mainframe, thereby freeing the mainframe to handle other tasks. Freeing the resources of a mainframe, approximately 30% for many TCP/IP for MVS file transfers, can mean savings equal to a tenfold return on the investment in the new controller and TCP/IP Offload application. The Model 3 when running with the new licensed program, Interconnect Controller Program (ICP) Version 3, performs twice as fast as the Model 1 due to better data handling and a powerful Intel 80486 microprocessor. This improved performance is especially attractive to users who need to share large data files, such as those used in scientific and engineering applications, with other users on the network. Also, the 3172 Model 2 is enhanced so that it can now send data across Token-Ring and Ethernet LANs as well as FDDI LANs. Model 2 enhancements, Model 3 (along with the TCP/IP for MVS Offload application), and ICP V3 will be available on September 25, 1992. Contact: Richard Tobacco - 3172 & TCP/IP Product Marketing DALVM41B(TOBACCO) ====================================================================== >(I)92216. IBMs commitment to OSF There was a recent request from one of the EMEA countries to quantify IBM's commitment to OSF. This information was to be used in a customer presentation. I passed the question on to Teresa Leone, who is with AIX Industry Relations in Austin. I think that her reply nets out our position extremely well and can be used in other customer situations also. Here it is: From the desk of: Teresa H. Leone, AIX Industry Relations Austin, Texas, T/L 678-3879; (512) 838-3879 IBM Internal Use Only Subject: IBM's commitment in OSF? Let me take a stab at how I position our commitments in briefings. First, the entire AIX lab and set of architects and programmers all work at implementing OSF code from the numerous technologies there. As far as financial commitment, the sponsor fees are the same for all OSF sponsors. There is not a differentiator there and I don't think a financial discussion is necessary to leverage our commitments. For the OSF/1 operating system. Actions speak louder than words, and unquestionably IBM has done more than HP or DEC and has more in common between AIX and OSF/1 than anyone else. Where we were beginning a new OS, we started with a pure OSF/1 1.0 base -- that is the AIX/ESA product. For AIX where we have an investment and a customer base already, we are migrating to OSF/1. However, we have more in AIX 3.2 than anyone else has on their commercially available products. Specifically, our AIX commands and libs are in common with OSF/1 -- we supplied them, and we continued our development relationship as the C/L supplier with OSF/1 1.1 and AIX 3.2 -- we are committed to keeping them convergent. We are the only vendor system shipping that is certified by OSF as conformant to the OSF/1 Application Environment Specification (AIX 3.2). We picked up the OSF/1 file tree structure in AIX 3.2 as well. DEC has a toolkit but it is not a commercially available system and when you ask if it would be compatible with any future OSF/1 system they would ship they say no. HP has said HP/UX will become AES compliant but not when. They've said nothing more. We have said we intend to trademark when OSF defines a OSF/1 trademark policy. As for DCE, we are integrator of DCE for OSF. We did that because we are so committed to the technology we wanted to build a technical team as quickly as possible with a strong core competency in this technology. We have said we will ship a full DCE product this year on AIX. As for Motif, we ship that today and are committed to it. Our CUA architecture team in the IBM Cary lab have done a set of work under agreement with OSF for their 1.2 release of Motif to keep the Motif Style Guide consistent with CUA 5 so that CUA users and Motif users have the same look and feel. We continue to work between those teams and OSF and are looking at cutting a further development agreement with OSF for Motif and CUA function. For DME, we are a technology supplier to the DME technology for SRC in AIX V3 and for the Data Engine out of Yorktown Research. We sit therefore on the OSF Architectural Board for DME and have a voice in that product as well. We have stated our intent to pick up DME technology in our AIX and SAA system mangement products and to have SystemView interoperate with DME. Mike Saranga from IBM serves as the Chairman of the Board for OSF. Donna Van Fleet as the Director for AIX Programming in Austin also sits on the Board from IBM. There is not a single OSF technology in development that we do not use or plan to use in our products and for which we do not have some role as a supplier or joint developer/integrator with OSF. Hope that helps. ====================================================================== >(U)92217. How do I see what processes are killed when out of paging space? Newsgroups: comp.unix.aix J Eric Townsend writes: > > Is there any facility in AIX 3.2 that lets me log/trap/trace process > kills by the kernel? In particular, I'm interested in kills that > happen as a result of the system running out of virtual memory. These are normally logged in the error log as 'PGSP_KILL' errors. ====================================================================== >(U)92218. Mwm color definitions on mono screens When using X servers that do have less than 256 colors, mwm causes problems because it uses a lot of the colors for itself. With the following lines in .Xdefaults the color hunger of mwm can be controled: Mwm*saveUnder: False Mwm*windowMenu: DefaultWindowMenu Mwm*buttonBindings: DefaultButtonBindings Mwm*menu*background: wheat Mwm*menu*foreground: black Mwm*background: black Mwm*foreground: wheat |Mwm*fontList: rom14 Mwm*activeForeground: wheat Mwm*activeBackground: black Mwm*ActivetopShadowColor: wheat Mwm*ActivebottomShadowColor: black ====================================================================== >(U)92219. HOTW: How do you log all your actions? SMIT creates a smit.log file - how to log the rest of your work. Using the SCRIPT command you can log all events of a shell session or a program in a file. This is usefull to exactly document step by step scenarios. $ script -a /home/kraem/tmp/logfile # start the log $ ....... # see logfile $ ....... # ........... $ exit # stop the logging $ pg /home/kraemtmp/logfile # contents of the log file Script command is started. The file is /home/kraem/tmp/logfile. $ ls -la total 1864 drwxr-xr-x 2 kraem system 512 Jun 10 14:49 . drwxr-sr-x 11 kraem system 512 Jun 10 14:39 .. -rw-r--r-- 1 kraem system 180 Jun 10 14:48 howto -rw-r--r-- 1 kraem system 58 Jun 10 14:49 logfile -rw-r--r-- 1 kraem system 122811 Jun 05 13:38 pvmexp.tar.Z -rw-r--r-- 1 kraem system 758831 Jun 01 17:59 xpguidv2.tar.Z $ exit Script command is complete. The file is /home/kraem/tmp/logfile. frank ;-) ====================================================================== ====================================================================== Live Free Or Die|: imp. 1. The state motto of New Hampshire, which appears on that state's automobile license plates. 2. A slogan associated with UNIX in the romantic days when UNIX aficionados saw themselves as a tiny, beleaguered underground tilting against the windmills of industry. The "free" referred specifically to freedom from the fascist design philosophies and crufty misfeatures common on commercial operating systems. Armando Stettner, one of the early UNIX developers, used to give out fake license plates bearing this motto under a large UNIX, all in New Hampshire colors of green and white. These are now valued collector's items. >92.07.03 Table of contents: (I)92220. IBM Announces High Availability Software for RISC System/6000 (U)92221. How do you find out if you run on a diskless machine? (I)92222. We do save Energy (FYI) (I)92223. IBM ANNOUNCES NETWORK QUEUEING SYSTEM/MVS (NQS/MVS) PROGRAM PRODUCT (U)92224. Using HP DeskJet 500C with RISC/6000 (I)92225. Distributed Computing Environment Documentation (U)92226. What caused the system to 888/crash? Use: ERRDEAD (U)92227. Using Xterm on AIX 3.2 without clobbering /etc/utmp (U)92228. Automounter fixes for 3.2.1 (I)92229. CATIA support for Gt4 and Gt4x (I)92230. GT4/GT4x doc (U)92231. To which lpp belongs this file? (AIX 3.2 version) (U)92232. How-To read/decode ARP output (U)92233. Useful info on re-sizing primary paging space (I)92234. NETWARE FOR AIX/6000 FROM IBM V3.11 - TUNING TIPS (I)92235. How to write an NCS server procedure (U)92236. A more colorfoul directory listing (I)92237. AEU - AIX Internals Overview Workshop - 3AIN203 (Europe) (I)92238. Announcing Euro-Unite '92. (U)92239. HOTW: Is the 'pg' (page) command too plain? ====================================================================== >(I)92220. IBM Announces High Availability Software for RISC System/6000 June 16, 1992 (US NEWS) IBM today announced the AIX High Availability Cluster Multi-Processing/6000 (HACMP/6000)*, software designed to support RISC System/6000 customers that depend on their computers for business critical applications. The HACMP/6000 software ties together two RISC System/6000 units in a clustered configuration, ensuring maximum availability of systems by allowing the computers to back each other up. IBM also announced that it will begin distributing the IBM AIX/6000* operating system via Compact Disc Read Only Memory (CD-ROM), which will make the product easier to install. AIX/6000 is IBM's implementation of the UNIX** operating system. In addition, IBM recently announced price reductions on RISC System/6000 memory upgrades of up to 41 percent. HACMP/6000 allows customers to choose from three levels or "modes" of high availability support, according to their requirements. In mode 1, HACMP/6000 provides fallover to a backup idle RISC System/6000 for quick restart of an application or subsystem if there is a failure with the primary processor. Each RISC System/6000 is active in mode 2, running its own unique application, but allowing one system to fallover to the other should a processor fail. In mode 3, the highest level of cluster support, the systems run concurrently, allowing single image access to data from both computers. This concurrent processing requires the IBM 9333 High-Performance Disk Drive Subsystem. Using HACMP/6000, customers also will receive greater use of their applications running on the RISC System/6000 by sharing the processor resources within the HACMP/6000 cluster, a feature that is unique in the UNIX marketplace. HACMP/6000 is supported by AIX/6000/3.2 and uses the Systems Management Interface Tool for installation, configuration and maintenance of the RISC System/6000 clusters. HACMP/6000 even allows systems administrators to make changes, add upgrades and do systems maintenance without affecting users. ClaM Associates Inc., an IBM Business Partner located in Cambridge, Mass., is working with IBM to provide customer installations and support for HACMP/6000. Major database vendors, including Informix, Ingres, Oracle, Sybase and independent software vendors, also are supporting their software on the HACMP/6000 platform. Oracle Corporation announced separately today that its ORACLE7 integrated with Parallel Server will support the HACMP/6000, noting that the IBM HACMP/6000 is an excellent example of loosely coupled systems where different processors cooperate even though they don't share the same memory. Planned availability for the AIX High Availability Cluster Multi-Processing/6000 is September 1992 for modes 1 and 2, and March 1993 for mode 3. Price will vary according to RISC System/6000 processor selected. * Trademark or registered trademark of International Business Machines Corporation ** Registered trademark of UNIX Systems Laboratories Inc. ====================================================================== >(U)92221. How do you find out if you run on a diskless machine? I think the best way to determine if you're a diskless machine or not is to execute the "bootinfo" command. "bootinfo" will look in the ipl control block and echo to stdout a number which corresponds to the type of device which was used to obtain the boot image from (ie., which device was booted off of). In order to get this information from "bootinfo", use the "-t" flag : bootinfo -t I don't know if there is a .h file which relates what is returned from bootinfo with a type of device, but here are what the returned numbers mean : 1 = disk boot 2 = diskette boot 3 = cdrom boot 4 = tape boot 5 = network boot In order to execute bootinfo, however, you must have root authority. -- Donald Long ====================================================================== >(I)92222. We do save Energy (FYI) IBM ACHIEVES NEARLY ZERO GROWTH IN WORLDWIDE ENERGY CONSUMPTION, SAVING $32 MILLION IN ENERGY COSTS June 17, 1992 (CORP NEWS) IBM's year-to-year energy consumption from 1990 to 1991 remained virtually flat for the first time in a decade, thanks largely to conservation efforts at IBM manufacturing and development sites worldwide. Energy-management programs helped IBM save more than $32 million in electricity costs in 1991. The unused 340 million kilowatt-hours cut carbon dioxide production associated with electrical power generation by some 210,000 tons. From an environmental emissions standpoint, that's equivalent to removing 50,000 cars from the road. IBM, which does business in more than 130 countries and operates 33 manufacturing plants worldwide, had energy costs of about $700 million in 1991 -- an increase of just 1.1 percent over the company's 1990 power bill. The minimal increase is significant in comparison to IBM's previous year-to-year jumps in energy consumption. The 1989-1990 increase, for instance, was nearly $60 million. Arthur J. Hedge Jr., IBM vice president, corporate environmental affairs, said he hoped to hold the line on energy consumption by rolling out further conservation programs. "The opportunities to conserve exist, and the know-how is there," he said. "The challenge is to leverage successful programs across the entire business." IBM facilities in Fujisawa and Yamato, Japan, Manassas, Va., Owego, N.Y., and IBM's Almaden Research Center in San Jose, Calif., were recently recognized by the company for significant energy savings. The Yamato development laboratory, which was designed and constructed for maximum energy efficiency, uses less than 70 percent of the electricity needed to operate comparable buildings. ====================================================================== >(I)92223. IBM ANNOUNCES NETWORK QUEUEING SYSTEM/MVS (NQS/MVS) PROGRAM PRODUCT June 16, 1992 IBM has announced the IBM Network Queueing System/MVS Version 1 Release 1. The Network Queueing System (NQS) protocol is a popular method for submitting batch requests to remote UNIX(TM) machines over a TCP/IP network. NQS/MVS(TM) expands this open systems solution to include the submission of batch requests to an MVS platform. NQS/MVS acts as a mediator between the NQS protocol and MVS(TM) JES2 services. NQS/MVS extends the standard NQS commands to include support for MVS. Users can submit, cancel, and check status of jobs on MVS directly from a UNIX workstation without the user logging on to TSO. A user can request that output be sent back to a workstation or remain on MVS for later reference. This is particularly beneficial if workstation users already were using NQS. Rather than learning new commands, users can use virtually the same commands to do batch job processing on remote UNIX and MVS machines. Typically, the batch request is written in MVS JCL but users can also use an alternate method for job submission that eliminates the need for them to write or use JCL. Customers can define a specific language for describing a job. A user creates a file containing this special language. When the job is submitted to NQS/MVS, the NQS/MVS user exit intercepts the job and passes it to a customer written translation program. The user's job is translated from the customer-defined language to JCL; NQS/MVS then submits the JCL to JES2 for processing. NQS/MVS (Program Number: 5695-168) was developed by the Technical Computing Solutions group within the Highly Parallel Supercomputing Systems organization, Enterprise Systems. For further information see Announcement Letter #292-313. For additional information, contact: BERNIE at KGNVMC Trademarks: UNIX is a trademark of UNIX System Laboratories, Inc. NQS/MVS is a trademark of the IBM Corporation MVS is a trademark of the IBM Corporation ====================================================================== >(U)92224. Using HP DeskJet 500C with RISC/6000 Turning your HP 500C into a Color PostScript printer. Here are the steps to be able to use the HP500C for color PostScript on a RS6K. 1) Connect your HP500C to the parallel printer port. 2) Configure your printer as a HP LaserJet II using SMIT. 3) Get the GhostScript (GS) 2.4.1 package from your favorite Free Software Foundation (FSF) source. 4) Compile GS with the RS6K options specified in the Makefile. Be sure to include the HP500C device support in the options. 5) run GS as shown gs -sDEVICE=djet500c -sOUTPUTFILE=outputfilename inputfile.ps where "outputfilename" is the file you want for the 500C printer commands and inputfile.ps is the color PostScript source. 6) issue the AIX command qprt -d p outputfilename where "outputfilename" is the 500C printer command file. This will send the 500C printer commands to the printer that you've specified with your environment variable PRINTENV. It also bypasses any default printer driver or translation tables used for the default printers. Documentation that comes with GS 2.4.1 tells you how to use the "gs" command to send your output directly to the printer, go figure. John ====================================================================== >(I)92225. Distributed Computing Environment Documentation The ITSC in Austin has received many requests for Distributed Computing Environment (DCE) documentation. ITSC-Austin is not able to provide this documentation but it can be obtained from the OPEN SOFTWARE FOUNDATION (OSF) or from IBM via VNET as explained below. Please note that IBM has the right to distribute an unlimited number of copies of the OSF DCE 1.0 documentation for IBM internal use. However, IBM can distribute documentation outside IBM only in conjunction with the sale of DCE software. To get the documentation set on tape or in hardcopy, type REQUEST DCEDOCS FROM DCEREQ AT AUSVM1 at the VM/PROFS command line. Note that this is the documentation from the OSF, not the IBM version, of documentation for DCE. Also, it is the DCE 1.0 version, not the DCE 1.0.1 version. (Still highly informative for learning about DCE and how it is used...) To obtain the OSF DCE 1.0 code (in source or binary form), type REQUEST DCEFORMS FROM DCEREQ AT AUSVM1. The royalties involved are explained in the package of information which will be sent in response. Ron Smetana, ITSC-Austin 19, June 1992 ====================================================================== >(U)92226. What caused the system to 888/crash? Use: ERRDEAD Ever wonder what caused your system to 888/crash? The ERRDEAD command extracts error records that were in memory and had not yet been written to the error log when the system dumped. Note: The ERRDEAD command REQUIRES that you have a dump device enabled. Typically this is /dev/rhd7. Example: #errpt -a | pg # what do we find in the error log ? #/usr/lib/errdead /dev/hd7 # any error records in the dump ? #errpt -a | pg # browse the error log - whatznew ? For additional information checkout the pub: DIAGNOSTIC PROGRAMS: SERVICE GUIDE; Chapter 2, "Reading Flashing 888 Numbers" ...... 2-2 inspired by: jk ====================================================================== >(U)92227. Using Xterm on AIX 3.2 without clobbering /etc/utmp Xterm has a severe bug which will clobber /etc/utmp. I have added the following lines of code to main.c: 1. include near the top of the file: #ifdef AIXV3 #define HAS_UTMP_UT_HOST #define HAS_BSD_GROUPS #endif /* AIXV3 */ 2. now search for CLOCAL, there is only one occurrence and add the lines I have marked with a >>: (and keep in mind, the | should be a pipe-sign) /* set some flags that should be on */ terminal_modes.c_oflag |= OPOST; /* set some flags that should be on */ >> /* set some flags that should be on */ >> terminal_modes.c_lflag |= ECHO; >> /* set some flags that should be on */ /* set some flags that should be off */ terminal_modes.c_cflag &= ~( CLOCAL ); <<< and this ~ remains a tilde /* set some flags that should be off */ 3. now recompile and xterm nomore clobbers utmp and allows input even if started in the background :-). It works for me; enjoy. regards, uwe untermarzoner ====================================================================== >(U)92228. Automounter fixes for 3.2.1 Get this ptf for the latest sun 4.1.1 automounter U404456 nfs320 IX26018 51189 9222 bosnet ====================================================================== >(I)92229. CATIA support for Gt4 and Gt4x We are pleased to announce that CATIA323 will support both Gt4 (8-Bit and 24-Bit) and Gt4X (8-Bit and 24-Bit) adapters starting September 92.(ref IBM Press Release) IBM and Dassault Systemes have agreed on a common strategy in the field of graphics adapters for CATIA on the RS/6000 platform. For a better understanding of this strategy, please find here after some technical guidance and Q/Answers. I will maintain this info in a separate file for future enhancements; So do not hesitate to contact me if you want to add/modify something. *-*-*-*-* Best regards. Have a nice day. *-*-*-*-*-*-*-* .----------------------------------------------------------------------. | E-Mail: FRANVM3(KRAEMERF) - VNET | | IBMMAIL(DEIBM27S) - IBM-Mail | | DE.IBMX400.IBMMAIL.KRAEMER.KRAEME - X.400 | | kraemerf@franvm3.vnet.ibm.com - Internet | '----------------------------------------------------------------------' ************************************************************************** ******* Technical Guidance **************************************** Dassault Systemes and IBM recommendations for IBM graphic adapters usage with CATIA solutions are as follows: Advanced Capability workstation: GTO adapter ------------------------------- This solution is recommended for all models of IBM RS/6000 systems supporting a CATIA application that requires superior graphics capabilities. It is Dassault Systemes intention to enhance CATIA in the future so that advanced GTO adapter features (such as the 24-Bit shading processor) can be exploited by CATIA to augment end user productivity and ease of use. We recommend the GTO model 1 (8-Bit) adapter to be used with CATIA323 and upper release levels. Integrated Capability workstation: Gt4x adapter --------------------------------- This solution is recommended when an integrated graphics adapter is required to provide a performance, price and functionality level superior to what exists today with the 5086 graphic solution. This new adapter will be compatible with the RS/6000 3XX and 5XX models. As for GTO, it is Dassault Systemes intention to exploit advanced adapter features such as 24-Bit shading processor. We recommend the Gt4x 8-Bit adapter to be used with CATIA323 and upper release levels. Low Cost Capability: Gt4 Adapter ------------------- This solution is recommended when low cost is the major or primary factor for customers seeking better overall graphics performance than is offered by the existing IBM 3-D Color Graphics Adapter for RS/6000 but lower than 5086. The Gt4 adapter is a full double buffer adapter (8-Bit and 24-Bit). We recommend the Gt4 8-Bit adapter to be used with CATIA323 and upper release levels. Nota: The Gt4 adapter is upgradable to the Gt4X adapter. ************************************************************************** Configuration guidance Questions/Answers ************************************************************************** 1. Why support Gt4/Gt4x starting September 92 and not at GA date ? Both IBM and Dassault Systemes are tuning the driver and microcode for Gt4x in order to achieve Gt4x performance better than 5086 in all cases. This means a lot of work on many different CATIA models and a great cooperation between Austin, Kingston, ICSC and Dassault Systemes. This tuning update will be available by September 92 ; The Gt4 adapter has the same architecture as the Gt4x adapter. CATIA support of Gt4 and Gt4x is announced today to be available 9/92 2.Why recommend the 8-Bit and not the 24-Bit adapters ? The 24-Bit adapters are not currently exploited by CATIA323; They occupy 1 more slot in the RS/6000. (The Gt4x 24-Bit adapters occupy 3 slots and are not pluggable into a 320H on a network environment, as the TokenRing or Ethernet card occupies 1 slot.) The Gt4 and Gt4x 8-Bit adapters have the double buffer feature. 3.GT4 8-Bit - Sabine 8-Bit/24-Bit comparison (sabine = 3D color graphic adapter) The GT4 8-Bit adapter simultaneously offers double buffer and usage of 125 colors in CATIA (5 standard CATIA colors + 120 user defined colors). Usage of double buffer in Sabine 8-Bit restricts the number of colors to the 5 standard CATIA colors. The GT4 8-Bit adapter offers a greater overall performance compared to the sabine 24-Bit adapter. The 5 standard CATIA colors are white, red, blue, green and yellow. 4.Gt4X - 5086 comparison Advantages of Gt4X vs 5086: The Gt4x is an integrated adapter, 5086 is not. The Gt4x is supported by graPHIGS which means support by Xwindows, allowing concurrent multi-windowing applications; 5086 does not which means that no more than 1 application may run on a 5086 at the same time. Gt4x graphics display list is not as limited as for 5086, so Gt4x is able to display CATIA models containing a great number of graphics elements. Gt4X performance will be higher than that of 5086, with similar performance on special worst case configurations/scenarios. The Gt4x 8-Bit adapter price is lower than 5086. Nota : Some graphics functionalities have not yet been included in graPHIGS and exploited by CATIA such as BP (CATIA buffer plot switch), peeling mode, digitizer support, local transformation during CATIA NC VERIF or other CATIA computation/verification. It is IBM and Dassault Systemes intention to incorporate new graPHIGS functions in the CATIA graPHIGS RS/6000 solution. 5.RS/6000 models (CPU processors) influence on graphics performance ------------------------------------------------------------------- 5.1 Local transformation (rotation, zooming) Local transformation are mainly treated by the adapters, so different RS/6000 models have low impact on them. 5.2 Buffer Refresh (BR) on graPHIGS adapters RS/6000 models have a great influence on the BR values. Looking at the Specmarks and the SPECint values gives a good indication of the CPU influence for the BR. Buffer Refresh on graPHIGS adapters consists of computing and converting the CATIA entities into graPHIGS entities and then displaying the results. This activity is mainly CPU consumption (Only 5 % of overall active processes are waiting for I/O on a 530). We are making our tests on a 520 to be in a worst case configuration for Gt4 and Gt4x. 5.3 Buffer Refresh on 5086 adapters RS/6000 models have an influence on 5086 BRs but not so important as for grapHIGS adapters. Buffer Refresh on a 5086 is treated differently as 5086 is a dedicated graphics terminal with computing facilities. (Around 30 % of the RS/6000 active processes are waiting for I/O -mainly the 5086 - on a 530). 6. Technical choice between 220-GTO and 32H-Gt4x (Gt4) ------------------------------------------------------ Local transformations (LT) are not as dependent on the CPU model as BR. GTO LT performance is greater than Gt4x and Gt4 one. Buffer refresh is directly related to the SPECmarks and the SPECint values and there is a significant gap between RS/6000 models. see examples below : 220 SPECmarks : 25.9 SPECint : 17.5 320H SPECmarks : 43.4 SPECint : 21.8 350 SPECmarks : 71.4 SPECint : 36.2 560 SPECmarks : 89.3 SPECint : 43.8 BR activities represent an important part of CATIA visualization (a lot of CATIA BR's are implicitly performed, for example when you select another CATIA function or add a CATIA element ). 32H-Gt4x (Gt4) is a preferred solution for an entry CATIA workstation. I cannot comment on pricing differences as I don't have all the elements right now. 7. Are Gt4 and/or Gt4x pluggable into a 220 ? --------------------------------------------- Answer is no. Helene Delage ICSC Paris ====================================================================== >(I)92230. GT4/GT4x doc There is a new performance document about the Gt4/Gt4x graphics adapters on the aixdoc disk. Request it with TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET GT4XPERF TERS3820. or use TOOLS SENDTO DALVM41B IBMPC AIXDOC GET GT4XPERF TERS3820. Then unterse it and you get a document in LIST3820 format which you can print on your local host printer. The POWER may be with you... Andreas Hermelink 29.6.92 ====================================================================== >(U)92231. To which lpp belongs this file? (AIX 3.2 version) #!/bin/ksh # # shell script to tell you which "lpp" contains a particular file or directory # syntax: whichlpp [path1] [path2] [path3] ... [pathN] # # All the spaces below are VERY important.... # # Parentheses - () # Square brackets - [] # Curly brackets - {} # Double quote - " # Single quote - ' # Back single quote - ` # Forward slash - / # Back slash - \ # # For more information, see InfoExplorer and odmget, inventory, and lpp. # -Mickey Coggins, # with TONS of help from the *amazing* Stephan Langenfeld ODMDIR=/usr/lib/objrepos for FILENAME ; do if [[ `basename $FILENAME` != $FILENAME ]] ; then stanza=`odmget -q"loc0 = $FILENAME" inventory` if [[ -z "$stanza" ]] ; then echo "Couldn't find "$FILENAME" with an exact search." echo "Try entering simply "\"`basename $FILENAME`\" fi else stanza=`odmget -q"loc0 like */$FILENAME" inventory` fi stanza=`echo $stanza` # converts all newlines to spaces # do it while some chars to process while (( ${#stanza} > 1 )) ; do # get right part of string, # which is the last stanza in the list tmpstanza=${stanza##*inventory:} lpp_ids=${tmpstanza#*lpp_id = } lpp_ids=${lpp_ids%% *} names0=${tmpstanza#*loc0 = \"} names0=${names0%%\"*} names1=${tmpstanza#*loc1 = \"} names1=${names1%%\"*} names2=${tmpstanza#*loc2 = \"} names2=${names2%%\"*} for id in $lpp_ids ; do name=`odmget -q"lpp_id = $id" lpp | grep name` name=${name#*name = \"} name=${name%%\"*} echo lppname: $name echo -n "location: $names0" if [[ x$names1 != x ]] ; then echo -n " hard links: $names1" fi if [[ x$names2 != x ]] ; then echo -n " soft links: $names2" fi echo done # chop off the last entry in the list stanza=${stanza%inventory:*} done done ====================================================================== >(U)92232. How-To read/decode ARP output Need the IP ADDRESS of a remote host? Use ARP. Curious if another system is on the local segment or remote? Use ARP. ARP (address resolution protocol) is one of the lesser known protocols that makes up the TCP/IP protocol stack. Example: $arp pippi pippi (19.21.4.YYY) at 50:00:xx:xx:xx:xx [token ring] rt=6b0:321:40 $arp syclone syclone (19.21.4.ZZZ) at 50:00:xx:xx:xx:xx [token ring] rt=630:321:40 Explanation: The RT field is the route (i.e. rings/bridges). The first byte is the routing control field. The rest is the rings and bridges used. Routing Control = BBBLLLLL DFFFrrrr B = Broadcast indicators L = Length bits D = Direction bits (0=left to right; 1=right to left) F = Larges Frame bits r = reserved bits 06B0 decodes: Non-Broadcast 6 bytes of routing info route is from right to left largest frame = 4472 321:40 decodes: From ring 032, bridge 1 to ring 040 Thanx to ST. ====================================================================== >(U)92233. Useful info on re-sizing primary paging space ENTER AT YOUR OWN RISC! Scenario: You have an RS/6000 on which you want to install a large application or the Munich TMSC demos. The primary paging space (hd6) is 80Mb. The secondary paging space (hd61) is 32Mb. The machine has 32Mb of system memory. The available free disk space is 20Mb less than you need. Every been in this situation (Mike Hall - raise your hand). The following info will let you re-define the primary paging space to the correct size and regain all that valuable disk space. This is only applicable on 3.2 systems. Follow these instructions carefully - especially the rebuilding of the boot logical volume image and make sure that this command completes before re-booting or it's re-install time! o Comment out the line in /sbin/rc.boot that activates /dev/hd6.Search for hd6. o Disable use of hd6 at IPL either through SMIT or using - chps -a 'n' hd6. o Rebuild the boot logical volume image with - bosboot -d/dev/hdisk# -a (where # is the boot disk number on the machine - usually 0). o Reboot the system using - shutdown -Fr o Remove the old hd6 paging space through SMIT or using - rmps hd6 o Create a new paging space of the correct size through SMIT or using - mkps -s'#' -a'' rootvg hdisk## (where # is the size of the new primary paging space in 4Mb partitions ## is the disk number where the primary paging space should be located - usually on hdisk0). If you use SMIT select activation on boot but not active now or you will not be able to do the next operation. o Rename this new paging space to be hd6 using - chlv -n hd6 paging## (where ## is the number of the paging space created - usually 00 if this is the first manually created paging space). o Edit out the reference to the old paging00 in /etc/swapspaces o Remove the comment from the "swapon" command in /sbin/rc.boot o Rebuild the boot logical volume image again as above. o Reboot the system using - shutdown -Fr These instructions are based on an append to the ISTHERE forum on IBMUNIX. I've modified them to a) remove typos b) provide AIX commands for all operations - you needn't use SMIT at all if you don't want to and c) provide a more orderly and definite series of instructions - the append was a bit conversational. From start to finish it took approx 12mins on a 320H - most of it is due to the two shutdowns. This method will also work on boxes with only 1 hard disk and therefore usually only one paging space, the primary one. Contrary to popular belief an RS/6000 will boot up without any paging space - no guarantees about running X and InfoExplorer though! Regards, Chris Thomas ====================================================================== >(I)92234. NETWARE FOR AIX/6000 FROM IBM V3.11 - TUNING TIPS NETWARE FOR AIX/6000 FROM IBM V3.11 - TUNING TIPS INTRODUCTION The objective of this flash is to provide a few tuning hints and tips for NetWare for AIX/6000 from IBM v3.11. The following is the result of initial studies conducted by IBM Austin. These items should be considered to be preliminary and subject to additional clarification. SUGGESTIONS FOR TUNING. 1. Use the burst shell whenever possible. NetWare for AIX/6000 provides a burst shell (bnetx vs the regular shell net3/net4). The bnetx (used with the packet burst protocol) command reduces the number of requests needed in large read or write requests. With one request, it can transfer up to 64K of data; whereas, using netx would require 1 request for each packet that's transferred. o To take advantage of the burst shell: a. Set "packet_burst = active" in /etc/netware/NWConfig on the AIX/6000 NetWare server (note: "packet_burst = active" is the default) b. Create a file called 'net.cfg' in the DOS clients home home directory and insert the following line of code: pb buffers = N (where N is the number or burst packets) o For burst shell, the client applications should ideally use data record sizes of 5632, 11264, 16896, 22528 bytes, ... (increment by 5632 bytes) if possible. Again the Austin lab experiments showed these record sizes achieve the best throughput and performance. o Experiment with the parameters. Initial field experience, for example, showed that when copying a large file you should use the burst shell (bnetx) and set pb buffers=2 in net.cfg. Other choices of buffers may fit your usage better. The point here is that you should try a different number of buffers to see which one is best suited for your client application in your environment. 2. For the regular shell, the client application should use a multiple of 1K (1024, 2048, 3072, 4096 bytes, ...) data records in order to get better throughput. The Austin lab experiments showed that a 1K data record had a 40% higher throughput rate than a 1152 byte (1K + 128) data record. 3. Check your mbuf usage by using the following AIX command: netstat -m If you get the reply "request for memory denied" (the number would be more than zero) change the mbuf allocation parameters. The following worked well for us: no -o lowclust=30 no -o lowmbuf=200 no -o thewall=4096 no -o mb_cl_hiwat=60 Note: mbuf is an AIX system memory pool 4. In a heavily used network you may be losing packets due to transmit receive queue overruns in the AIX/6000 environment. Use SMIT to increase the Ethernet and Token-Ring transmit and receive queue sizes to the maximum allowed values. This should reduce the chance of packet loss due to the transmit underrun and receive overrun queue. Issue the following AIX command to check and see if you have lost packets: netstat -v Review the 'transmit underrun' and 'receive overrun' fields. 5. On the AIX System make sure you have the right number of ncp_engines activated based the number of active clients you have. It is recommended that you use one ncp_engine to serve every 10 clients (e.g. use 5 ncp_engines if you have 50 clients). Each ncp_engine will continuously poll to see if there are any requests to serve. By using too many clients per ncp_engine you can cause severe polling overhead. 6. Proper allocation of AIX shared memory can improve performance. For a complicated AIX application, it is recommended to set shared memory size and file size(shm_size = and fs_shm_size = 4096*1024 which is 4M) in following file " /etc/netware/NWConfig" on the AIX NetWare server. 7. As in most applications, having enough memory is very important. In general you should have a minimum of 32 MB of memory on your AIX/6000 NetWare server. 8. Putting too many files (more than 1500) in a single directory on the server can create additional overhead which will affect the "inodes file". Spreading your files across across multiple smaller directories will result in improved performance. 9. Adding and deleting files on the AIX Netware server leaves data structures that will cause additional overhead (this too affects the "inodes files"). Cleaning up a directory that has had lots of activity will result in improved performance. You should: a. save the files b. remove the directory c. make a new directory d. copy the saved files back. Directories will tend to grow over a long period of time. Even when a file is deleted from the directory there's still a hidden entry in the directory. 10. If your client application allows, avoid unnecessary opening and closing of files that are on the AIX NetWare server. Once client files are opened, leave them open until you are finished with processing. Continuously opening and closing a file uses extra CPU cycles on the AIX NetWare server. SUMMARY This discussion is based on preliminary data from IBM Austin and should be considered general tuning hints. Implementing these suggestions will not guarantee improved performance. Additional tuning information will be published as available. TRADEMARKS: o AIX, IBM, RISC System/6000, PC-DOS, are registered trademarks of International Business Machines Corporation. o NetWare is a registered trademark of Novell, Inc. o Ethernet is a registered trademark of Xerox Corporation. REFERENCES: The softcopy publications are not available through InfoExplorer. The following publications are available by ordering them with numbers: SC23-2422 NetWare for AIX/6000 from IBM v3.11 NetWare Concepts SC23-2419 NetWare for AIX/6000 from IBM v3.11 Installation SC23-2420 NetWare for AIX/6000 from IBM v3.11 System Administration SC23-2421 NetWare for AIX/6000 from IBM v3.11 Utilities Reference SC23-2423 NetWare for AIX/6000 from IBM v3.11 User Basics for DOS Workstations SC23-2424 NetWare for AIX/6000 from IBM v3.11 Troubleshooting and System Msgs SC23-2428 NetWare for AIX/6000 from IBM v3.11 Print Server FLASH 2056 A Comparison Between NetWare for AIX/6000 and Native NetWare v3.11 ====================================================================== >(I)92235. How to write an NCS server procedure Abstract : NCS server example Status : Running fine on AIX 3.2.1 Get the info via TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET NCSSERV TERS3820 or TOOLS SENDTO DALVM41B IBMPC AIXDOC GET NCSSERV TERS3820 Please Note: ------------ This program shows how to write an NCS server procedure. It has implemented some nice features like writing a log file and using the NCS PFM feature. If you use this program in connection with your own code you have to change the word INTERFACE to the name of your interface defined in the file. Also you have to append the functions that your client program will call via RPC at the end of the file. ====================================================================== >(U)92236. A more colorfoul directory listing Using this awk filter on a hft or aixterm will diplay executables, directories and ordinary files in different colors. #!/bin/awk -f colordir #@(#) COLORDIR Version 1.0; Doug Ranz Wednesday, July 01, 1992 09:28:06 EDT # # Simple color directory listing program by John Duglosz # # Modified By: Doug Ranz Wednesday, July 01, 1992 09:28:06 EDT # Modified By: afx Friday, July 03, 1992 14:58:00 EDT # # # Usage: ls -F | cdir # # Hint: use a bsh/ksh function or a csh alias # For example in your ~/.kshrc file: # lc () { # ls -F $* | colordir # } # # [ = open squere bracket # ] = close squere bracket # | = vertical bar # function lastchar() { return substr($0,length(),1); } # test code # { print $1 " ends in " lastchar(); } BEGIN { ESC="\033" # define escape color["*"]= ESC "[32m"; # executable: green color["/"]= ESC "[31m"; # directory: red color["normal"]= ESC "[37m" ESC "[11m"; } { print color[lastchar()] substr($0,0,length()-1) color["normal"] } # the end ====================================================================== >(I)92237. AEU - AIX Internals Overview Workshop - 3AIN203 (Europe) If interested, please enrol through your country education coordinator as usual. COURSE ANNOUNCEMENT Dear coordinators, We are pleased to announce the following workshop : Course name : AIX Internals Overview workshop Course code : AEU-3AIN203 Dates : September 7 - 11 (5 days) Class Manager : J. Simons (SIMONS at BRUVMIS1) Class Secretary : C. Monjoie (MONJOIE at BRUVMIS1) AEU - AIX INTERNALS OVERVIEW WORKSHOP - 3AIN ____________________________________________ COURSE CODE: 3AIN ITIRC CNC: SKILL LEVEL: 3 PARTICIPANTS : SEs and Professionals who will Diagnose and fix AIX Internals problems Prerequisites : AIX Skill level 3, Significant C lan- guage experience COURSE OBJECTIVES : After completing the course, the student should be able to analyse and specify internals malfunctions and diagnose AIX problems on all platforms. CONTENTS/AGENDA : o Structure of AIX Kernels o System Call Interface o Process Management o File Subsystem o I/O Subsystem o Memory Management o Interprocess Communication o Networking Issues o Persistent Storage Management DURATION : 5 DAYS FIRST DAY START TIME: MORNING ====================================================================== >(I)92238. Announcing Euro-Unite '92. We will be hosting a European IBM internal UNIX Internal Technical Exchange on September 22/23/24 at Hursley this year. Please would you inform other UNIX users at your site of this conference. The registration request and call for papers can be found in the UNITE FORUM on the IBMUNIX conference disk, appended on May 12th, but here is a brief extract: Euro-Unite! '92, the IBM Unix European Internal Technical Exchange, is soliciting papers, tutorials, and panel discussions on Unix. Key areas of interest include, but are not limited to: Unix Operating System and Application Programming Distributed Computing Environment for all platforms Administration Network Management Supporting Large Numbers of Workstations Writing MOTIF Applications User Interfaces (X, Motif, etc) Programmer Development Using UNIX Software Development Environments Software Development /Office Tools Andrew File System & ATK any other open-systems or Unix-related topic Papers may be about the use of any flavor of Unix or interconnection of Unix to other mainframes or operating systems. While these are the key areas, we are interested in any germane paper and each abstract will be considered on its merit. The intention of Euro-Unite! is to provide and interchange ideas among programmers and system administrators whose job involves Unix. Papers may be new material, work in progress, or material previously published elsewhere. Presentations should be no longer than one hour in length. Many thanks, and I hope to see you here in September! Mike Prince. (MIKE at HURSLEY) ====================================================================== >(U)92239. HOTW: Is the 'pg' (page) command too plain? The 'pg' command seems to have many underutilized options. These options permit you to alter the behaviou