>93.08.11 Table of contents: (I)93202. AIX 3.2.4 availability notice (U)93203. Mulitmedia mail on the /6000 (I)93204. Send mail on a bad error being logged (I)93205. AIX NetView/6000 vs the Competition -- New MKTTOOLS Package (I)93206. IBM Internal access to Electronic Customer Support for AIX (I)93207. EUROPEAN RS/6000 REFERENCE DATABASE (U)93208. Beta parallel port device driver (U)93209. Concert/C: A Language For Distributed C Programming (I)93210. DFS problem determination class in La Hulpe (I)93211. DFS installation and administration calss in La Hulpe (U)93212. Cabeling to share a 9334-501 between two systems (U)93213. AIX GDS Early Program Code Availability (U)93214. Yet another script to create man pages out of InfoExplorer (I)93215. Euro-Unite| '93 Announcement and Call for Papers (I)93216. Writing deamons the easy way (U)93217. Remote mksysb pitfalls and solutions (U)93218. List of available PTFs (I)93219. Sources of AIX information in Germany (I)93220. Soft graPHIGS Beta Program (U)93221. Getting the host name of the remote machine you are logged in from ====================================================================== >(I)93202. AIX 3.2.4 availability notice *********************************** **** IBM INTERNAL USE ONLY **** *********************************** Dear AIX Support Manager, The following information has been made available to you by AIX Software Development in Austin, Texas: The 3.2.4 PMP is again availableÙ The new images have been sent to Copenhagen, but I understand that we may have missed the daily processing, so the PMP may not be available in some countries until Monday, 19 July 1993. If you have questions, send a note to Dennis Lee (LEEDP at AUSVM8). The following is a description of the problem and a possible circumvention. ********************************************************* A problem was discovered in the AIX 3.2.4 Preventive Maintenance Package that will cause some systems to fail to IPL with either 551 or 552 in the LEDs. The problem occurs in the "ipl_varyon" program, used to bring the root volume group on-line. On systems with a large number of disks, the memory usage of this program could exceed the actual amount of memory in the system, causing the failure. The PE PTF is U419397, superseded on the 3.2.4 update by U418345. The APAR number for the 551/552 problem is IX37683, which has been fixed in PTF U420925. The fix is now available and has replaced U418345 in the PMP. On systems with externally powered disks, it may be possible to use the following circumvention. 1) Power off any disks that are not part of rootvg. 2) Boot the system. Any volume groups that are on the powered- off disks will fail to vary on. 3) Power on all attached disks. 4) Configure the disks with the command: cfgmgr -s 5) Vary on the volume groups that failed to vary on in step 2 using the command: varyonvg VGname Repeat the varonvg command for each volume group that is not varied on. 6) Run fsck on any 1 filesystem in each volume group varied on in step 5. You can get a list of the filesystems using the command: lsvg -l VGname The output will be similar to the following: othervg: LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT loglv00 jfslog 1 1 1 closed/syncd N/A lv00 jfs 20 20 1 closed/syncd /test Run fsck on any filesystem in the volume group using the command: fsck /FSname In the previous example, you would run: fsck /test Repeat the fsck command for 1 filesystem in each volume group varied on in step 5. 7) Mount the filesystems from the varied on volume groups using the command: mount all The mount all command will attempt to mount all filesystems that are normally mounted at IPL. It is normal to receive error messages for filesystems that are already mounted. In some cases, the circumvention will not work. For example, if all disks on the system are part of rootvg, or if the disks are not externally powered. In that case, you'll need to apply PTF U420925 in service mode using the following procedure. 1) Turn the key to service and boot the system from alternate media such as boot diskettes, a bootable tape, or CD-ROM at the same level of AIX as is installed on your system. 2) Select the maintenance shell from the menu (option 5 for AIX 3.1, option 4 for AIX 3.2). 3) Determine the hdisk# to use with the getrootfs or /etc/continue command. If you have only one disk, then "hdisk0" is the proper hdisk# to use. If you have more than one disk, run the command: lqueryvg -p hdisk# -At  grep hd5 for each hdisk# (hdisk0, hdisk1, etc.) until you get output similar to: 00005264feb3631c.2 hd5 1 The exact output you get will be different but will be similar to: large_number.x hd5 1 You may find more than one disk has this output. These will all be disks which belong to the root volume group. You may use any of the disks identified to be in rootvg in the following step. 4) Bring the root volume group on line using one of the following commands: For AIX 3.1: /etc/continue hdisk# For AIX 3.2: getrootfs hdisk# 5) Install the fix for U420925 using the command: installp -BXagqd /dev/rfd0 all 2>&1  tee /tmp/installp.out 6) Turn the key to the normal position and reboot the system using the command: reboot FROM AIXINFO at AUSVM6 ====================================================================== >(U)93203. Mulitmedia mail on the /6000 Subject: UltraCom Personal Media Pilot (TM) From: douga¹wixer.bga.com (Doug Ashbaugh) Organization: Real/Time Communications The IBM Risc System now knows MULTIMEDIA| UltraCom Incorporated is proud to announce an advanced electronic communication program for the AIX operating system. The package allows multimedia email communication among users and workgroups. Electronic mail capabilities including composition, transmission, and reception of audio, video frames, scanned documents, btmaps, text files and postscript files. The product is priced aggressively at only $279/user (10 user lic). Further information and full function demos are available from the following internet sites: ftp.uu.net : vendor/MetaCard/ultracom fto.metacard.com : MetaCard/ultracom UltraCom Incorporated Austin, TX (512) 339-8557 email: ultracom¹wixer.bga.com ====================================================================== >(I)93204. Send mail on a bad error being logged Ok, this works for sending mail when an error is logged. The approach I've used is to get notified on all errors, and filter them from the script that gets the notification. Here's the ODM stanza to use and add with "odmadd" errnotify: en_name = mailerrs en_persistenceflg = 1 en_method = "/usr/local/bin/mailerr $1 $2 $3 $4 $5 $6 $7 $8 $9" Now, write /usr/local/bin/mailerr something like this: #|/bin/sh # Mail errors to $user user= mach=`uname -n` errseq=$1 errid=$2 # List of error to exclude # unwanted="REBOOT_ID ERRLOG_ON ERRLOG_OFF CORE_DUMP" unwanted="0xfc1960ce 0x9dbcfdee 0x192ac071 0x0f27aae5" for i in $unwanted do Ü $i = $errid ð && exit done errpt -a -l $errseq Ù mail -s "Error $errlabel Occurred on $mach" $user Now, just use odmadd to add the stanza and you should be in business. Please let me know if this doesn't work. -- Jim Shaffer ====================================================================== >(I)93205. AIX NetView/6000 vs the Competition -- New MKTTOOLS Package A new package has been added to MKTTOOLS in order to provide marketing with information that enables them to more effectively market against NV/6000 competitors. The package can be found on MKTTOOLS under the name of NV6KCOMP. It contains documents and presentations related to NV/6000 competitors. The NV6KCOMP package currently consists of: FName FType Description -------- -------- -------------------------------------------- ATULREP TERS3820 * Kaptronix Inc., consultant report dated 6/93 * that discusses and contrast three SNMP network * management systems: * - HP: OpenView * - IBM: AIX NetView/6000 * - SunConnect: SunNet Manager * Note: * This report is labeled Kaptronix Copyright. * Author's permission was given to distribute * on IBM MKTTOOLS. *********************************************** VALUEADD TERS3820 * An IBM value add presentation of IBM * enhancements made to OpenView in NV/6000 V2. *********************************************** NV6KVSHP TERS3820 * Comparison of NV/6K V2 and HP: OpenView 3.1 * functions (text only). *********************************************** SCREENS TERS3820 * Comparison of NV/6K V2 and HP: OpenView 3.1 * (with screen comparisons). *********************************************** As additional materials are developed in this area they will also be added to this package. Subscribe today by entering the following command from your VM screen: TOOLCAT MKTTOOLS or TOOLS SENDTO USDIST MKTTOOLS MKTTOOLS SUB NV6KCOMP PACKAGE >> Note: Existing documents and presentations that use to reside on >> MKTTOOLS under the name of NV6KVSHP have been consolidated and moved >> into this new package in order to easy access and search capabilities. >> NV6KVSHP will be deleted from MKTTOOLS. ====================================================================== >(I)93206. IBM Internal access to Electronic Customer Support for AIX On July 13, 1993, we announced (as part of the AIX 3.2.4 announcement) an electronic support to allow customers to obtain fixes via the Internet. A similar service is available to IBM'ers who have Internet access (either IBM internal Internet or external Internet). This service will allow you to: Download current versions of IBM software for AIX/6000 Download AIX fixes The service costs $400/year for each user. For further information on the service please conact Claudia Schroedl at tie line 695-4276,PKMFGVM3(CLAUDIA) or Bob Prince,tie line 793-0143, AUSVM8(PRINCE). Additional information on this notice, contact: RHQVM01(GOLDSTIN) ====================================================================== >(I)93207. EUROPEAN RS/6000 REFERENCE DATABASE IBM INTERNAL USE ONLY EUROPEAN_RS/6000_REFERENCE_DATABASE. I am pleased to announce that there is now a Reference Database set up containing European RS/6000 references. It can be found on COMP on EHONE. Now, anyone who has access to the COMP database can search for references to help them win their bids. Instructions on how to find references are attached. So, if the Prospect is in: MANUFACTURING, DISTRIBUTION, DESIGN, TOURISM, RESEARCH or are: A UNIVERSITY, A FOOTBALL CLUB, A LIBRARY, BUILDING HELICOPTERS or use: ORACLE, SYBASE, UNIPLEX, INFORMIX, CATIA, CADAM, FDDI, PICK or have: NCR, HP, SUN, DEC or want to use: HACMP, PARALLEL PROCESSING, ETHERNET, TRN, NETVIEW/6000, IMAGING this database can now be searched to find examples to use as references. Full STAIRS search capabilities are available. All references are in English. Today, there are over 100 references available, and more will be added shortly. Currently, they are from Finland, Norway, Denmark, France, Switzerland and UK. We will be expanding the number of countries contributing. Please encourage your marketing people to add their reference accounts to the list by sending the details to me. Please distribute this to your AIX community. Any questions regarding the database should be addressed to myself. PAT KENNEDY AIX Systems Marketing - EMEA WARVM8(KENNEDP) Tel: 44 256 344327 IBM INTERNAL USE ONLY HOW_TO_USE_THE_COMP_DATABASE_TO_FIND_REFERENCES. The first screen available once you have logged on to COMP is the one you use to describe the search argument you wish to use to find information in the COMP database. COMP contains a wide variety of competitive information, not just references. To find European RS/6000 references you must key the following: FIELD. ENTRY. PRODUCT RS/6000 CATEGORY EURO TYPE REFE The above entries will obtain all of the European RS/6000 references on the database. If you want to be more specific you should add a description in the SEARCH WORDS field, for example ORACLE or UNIVERSITY or CATIA, as in a normal STAIRS-based search. This will reduce the number of "hits". There are also references for United States Customers in this database. If you want to search on them leave the CATEGORY field blank. Successful searches will produce a list of Customer details to view. You can select the ones you wish to look at by placing a "s" beside them. PLEASE NOTE: THESE REFERENCES HAVE BEEN PROVIDED BY SALESREPS AND SYSTEMS ENGINEERS FOR THE BENEFIT OF OTHER IBM'ers WHO ARE LOOKING FOR CUSTOMER NAMES TO USE IN A BID SITUATION. HOWEVER, YOU SHOULD ALWAYS CHECK WITH THE PEOPLE NAMED AS CONTACTS BEFORE QUOTING THE CUSTOMER'S NAME TO YOUR PROSPECT OR TRYING TO ARRANGE A VISIT. CIRCUMSTANCES CHANGE. TODAY'S REFERENCE CUSTOMER MAY BE TOMORROW'S UNHAPPY CUSTOMER, SO FOR YOUR OWN BENEFIT YOU SHOULD CHECK THE LATEST STATUS. If you need assistance to gain access to the COMP database you should contact your country COMP representative. If you are unable to do that please contact me, Pat Kennedy - WARVM8(KENNEDP). ====================================================================== >(U)93208. Beta parallel port device driver I am workin in conjunction with AIX devlopment on a mini-beta program for testing a new design for the parallel port device driver, which most people hook up to their printers. This code is VERY beta, but it seems to work well at the four sites we've tried it at. It has significant performance improvements in terms of not bogging down the CPU when large print jobs are sent to the printer. If you feel you've got a customer who would be willing to try this (with the understanding that if they call customer support, they get NO help) then contact me. -- The views expressed are my own. They do not represent IBM. Johnny Shieh (shieh¹racerx) Worker Bee, AIX Field Quality (level 3) VNET: SHIEH at AUSVM6 Internet: shieh¹aixwiz.austin.ibm.com Phone:(512) 838-3357 tie line 678-3357 ====================================================================== >(U)93209. Concert/C: A Language For Distributed C Programming Joshua Auerbach, Arthur Goldberg, German Goldszmidt, Ajei Gopal, Mark Kennedy, Josyula R. Rao, James Russell €jsa,artg,gsg,ajei,mtk,jrrao,jrussellõ¹watson.ibm.com IBM Research July 1993 We announce availability of the Beta release of Concert/C, a language that extends ANSI C with support for distributed programming. Concert/C runs on Unix machines. We're making it available to all IBM sites. It will also be made available outside IBM (for noncommerical use only) under the terms of the research division's experimental software distribution agreement. Inside IBM, it is available via ftp, afs and AIXTOOLS. SUMMARY Concert/C supports distributed C programming. Programmers write a program's local logic in standard C; they write its distributed logic in Concert/C's powerful operations. Concert/C systems are composed of communicating processes. A process is an executing sequential C program. The language provides primitives to create and terminate processes, establish communications connections among them, and communicate between them. The programmer explicitly expresses parallelization and distribution. Concert/C simplifies interprocess communications (IPC) programming by integrating it deeply into the language. Concert/C supports RPC and asynchronous messaging. Communications takes place over a `binding' in one process connected to a message queue (called a `port') in another process. A binding is simply a C pointer to the appropriate type of port. A pointer to a function with an associated port provides the capability to make an RPC on the function. Asynchronous messages are communicated by the primitives `send' and `receive'. All C data types can be transmitted in IPCs. Concert/C can transmit C arrays, character strings, and complex data structures containing pointers. Both RPCs and asynchronous sends are type checked at compile time. Concert/C adds process management to C. A create operation creates a new process and returns the parent process a handle to the child and a binding over which it can communicate with the child. The programmer can easily control the child's location, the relationship of its address space to other processes, and its other important characteristics. Systems of processes can evolve their interconnections in several ways. They can pass bindings in IPCs and store bindings in files and other external repositories. For more technical detail, see the documentation and papers. PLATFORMS The Concert/C Beta prototype runs on Unix systems (specifically AIX 3.2 on RISC System/6000s and SunOS on Sun4s). It should be easy to port it to other Unix's. We encourage you to forward requests for ports to us. We will try our best to see that the port gets done. An OS/2 implementation and a run-time that communicates via OSF/DCE exist, but are insufficiently tested to be included in Beta. OBTAINING CONCERT/C On AIXTOOLS, request CONCERT PACKAGE. Download CNCRT_B1 TARZBIN as cncrt.B1.tar.Z and proceed as for the other methods. The system is also available (to IBM internal users) via anonymous ftp from titanic.watson.ibm.com. cd pub/concert get cncrt.B1.tar.Z uncompress untar follow instructions in INSTALL If you have afs at your site, you may also be able to obtain concert as /afs/watson/projects/dsst/concert/dist/cncrt.B1.tar.Z. Once you have it, proceed as for the other methods. The external version is quite similar to what we are giving out internally. Despite this fact, please refer potential external users to us. Any copy which you receive via internal channels is IBM Internal Use. DOCUMENTATION The documentation includes installation instructions, the Concert/C Manual, the Concert/C Tutorial, the Concert/C Specification, and several technical papers. All program examples from the tutorial are also included. CONDITIONS AND SUPPORT We emphasize that we're distributing a BETA version of Concert/C. It contains known bugs (see the BUGS file). You may uncover bugs yourself. We would like you to report suspected bugs. Please try to isolate the suspect Concert/C bug from the rest of your code and send us the simple example. Concert/C is prototype research software and will be supported as such. We will respond as best as possible to user problems. We want happy and productive Concert/C users. However, we are a small group intent on continuing our research, so we may be unable to respond quickly. INTERACTING WITH US If you plan to write Concert/C programs, please let us know. Briefly tell us what you plan to do. We'll add you to the Concert/C mailing list and inform you of bugs, bug fixes, and proposed language changes. concert-c¹watson.ibm.com (if you are using internet mail) concrt-c at watson (if you are using VNET or BITNET mail) The Concert Project, H1-A17, Box 218, IBM Research Center, Yorktown Heights, NY 10598 voice: 914 784-7948 FAX: 914 784-7455 All trademarks are recognized trademarks of their respective companies. Respectfully submitted, Josh Auerbach ====================================================================== >(I)93210. DFS problem determination class in La Hulpe From: Veronique Carlier European Int. Services Company -EIS P.T.E. La Hulpe - BELGIUM CARLIER/BRUVMIS1 Phone: 32.2.655.5552 Fax : 5739 Subject: 4DFU301 - DFS Problem Determination - September 9 CSE - DFS PROBLEM DETERMINATION - 4DFU ______________________________________ COURSE CODE: 4DFU SKILL LEVEL: 3 PARTICIPANTS : This workshop complements the basic DFS Administration workshop (4DFS) and will benefit participants already familiar with DCE and DFS installation and adminis- tration from workshops like 4DFS or from DFS case ex- perience. COURSE OBJECTIVES : This 1-day workshop is a DFS technical update covering DFS problem determination and problem source identifi- cation. It will focus on the problems that occur dur- ing installation and administration of DFS. CONTENTS/AGENDA : The contents of the workshop will evolve following the enhancements of DFS and the current technical issues and skills required in customizing it. DURATION : 1 DAY PRICE : 18.500 BEF DATES : September 9 Regards Veronique ====================================================================== >(I)93211. DFS installation and administration calss in La Hulpe CSE - DFS INSTALLATION AND ADMINISTRATION - 4DFS ________________________________________________ COURSE CODE: 4DFS . SKILL LEVEL: 3 COURSE OBJECTIVES : This 3-day workshop covers the DFS component of DCE. Its purpose is to provide the DCE administrator with the needed skills for configuring and managing the fundamentals of Distributed File Service. The delivery methods are balanced between : o in class presentations of the major concepts o in class activities extending the knowledge into practice o guided hands-on for the practice of the commands and mechanisms. CONTENTS/AGENDA : The contents of the workshop will evolve tracking the current features of DFS. The present distribution of the topics on the 3 days is as follows : o Day 1 : DFS overview, DFS architecture and mech- anisms o Day 2 : DFS config, DFS filesets, DFS processes, File Server o Day 3 : DFS Client, DFS admin miscellaneous and review DURATION : 3 DAYS PRICE : 55.000 BEF DATES : September 6 - 8 Regards Veronique ====================================================================== >(U)93212.Cabeling to share a 9334-501 between two systems The diagram and notes below should explain what cables are needed to share a 9334-501 Disk Expansion Unit between two systems. 9334-501 Differential SCSI Twin-Tail Cabling -------------------------------------------- 8.0 to 4.75 Mtr 4.75 Mtr Diff Diff SCSI-2 Deskside SCSI-2 Deskside Cable Select #9235 Cable #2935 Ù Ù ___________ ____________ Ù Ù Ù Ù _ Ù Ù Ù Ù _ SCSI-DE -- Ž / Ù Ù Ž / -- SCSI-DE Y-Cable ___Ž/___ __Ù__Ù__ ___Ž/___ Y-Cable #2422 Ù Ù Ù Ù Ù Ù #2422 Ù Ù Ù Ù Ù Ù Ù AdapterÙ Ù 9334- Ù Ù AdapterÙ Ù #2420 Ù Ù 501 Ù Ù #2420 Ù Ù Ù Ù Ù Ù Ù Ù________Ù Ù________Ù Ù________Ù RISC 560 9334-501 RISC 560 Notes: 1. For HACMP configurations, the differential terminating resistors U8 and U26 must be removed from both of the SCSI-2 Differential adapters (#2420). 2. Each SCSI-2 Differential Y-Cable comes with a terminator, which must be attached to the open end of the cable. The other end of the Y-Cable attaches to the Differential SCSI-2 Cable you have chosen. 3. In a 2-system twin-tailing configuration, the use of standard length SCSI-2 Differential cables would be supported. It is suggested to use shorter cables if possible to allow for future expansion. Total supported cable length for the bus is 19 meters. Other cable lengths are: Y-Cable .765 Meters 9334 Internal Cabling 2.6 Meters vk ====================================================================== >(U)93213. AIX GDS Early Program Code Availability GLOBAL DIRECTORY SERVICE FOR AIX EARLY PROGRAM CODE AVAILABLE _____________________________________________________________ July 30, 1993 OPPORTUNITY: Today, IBM is announcing the availability of the GLOBAL DIRECTORY SERVICE for AIX* (AIX GDS) early program code for the RISC System/6000*. In today's distributed environments, applications and services can easily locate information worldwide via the GDS replicated, distributed database provided by this early program code. Function in this code enables IBM internals, customer software developers and independent software vendors to gain experience with the AIX GDS service. Further, this code program promotes application prototyping, development and testing activities while providing feedback to IBM. This early program code should NOT be used in production environments. Delivery of this early program code will be accomplished over INTERNET using the TCP/IP protocol via FTP. FEATURES and FUNCTIONS: The AIX GDS code is obtained from the Open Software Foundation (OSF)** and is a port of that code to the AIX workstation. AIX GDS is based on the CCITT X.500/ISO 9594 (1988) international standard and supports the X/Open** Directory Service (XDS) and X/Open OSI-Abstract-Data Manipulation (XOM) API's. These API's allow an application to manipulate objects in either the X.500 directory or Cell Directory Service (CDS) of the Distributed Computing Environment (DCE) from OSF. X.500 is a worldwide naming standard that allows organizations to globally share names and thus share objects. X.500 is extensible and provides a standard way of accessing names. The DCE Cell Directory Service is compatible with X.500 directory services, and provides mechanisms to allow DCE users to share information, services and resources on a worldwide basis. EARLY PROGRAM CODE SYSTEM REQUIREMENTS: Hardware environment + A RISC System/6000 POWERstation or POWERserver with display + A Token-ring or Ethernet LAN adapter card that supports TCP/IP or X/Open Transport Interface (XTI). + 32MB memory recommended + An empty temporary directory with 35MB hardfile space is required to contain the AIX GDS code package yet allow expansion of the code during the installation process. - The AIX GDS code package to be transmitted via INTERNET will be approximately 10MB. Publications supplied with this code package are in PostScript** format (900 pages). Software environment + IBM AIX Version 3.2.4 for RISC System/6000 + IBM AIX DCE Version 1.2 (required only if using XDS/XOM API to access DCE Cell Directory Service). ORDERING INSTRUCTIONS: The early program code package can be ordered today and is available worldwide. All customers will be required to sign an IBM Agreement for Test of IBM Program Materials. Installation is allowed on up to 6 machines in the customer enterprise. Code program interfaces and documentation are available in U.S. English only. To be considered for this early program code, submit the following information either via FAX to (512) 838-4002, Attn: "Dept 459 - AIX GDS" or via a PROFS note to DCEREQ at AUSVM1 or via INTERNET E-mail to dcereq¹vnet.ibm.com: + Specify you wish to receive the AIX GDS early program code. + Company Name: + Company Address: + Company Technical Contact Name and Phone Number: + Company FAX number: + Company INTERNET ID for E-mail support contact: You will then be FAXed the IBM Agreement to Test IBM Program Materials with instructions to qualify for this early program code. Once approved, you will be FAXed instructions to accomplish code delivery over INTERNET using the TCP/IP protocol via FTP. TECHNICAL SUPPORT: All participants receive no-charge technical support for this early program code via INTERNET E-mail. Any E-mail received by the INTERNET support ID will be forwarded to all participants at their specified company INTERNET ID. This process allows early code support information to be known to everyone. All E-mail sent to the support ID below will become public information. This IBM support will be provided on a 'reasonable efforts' basis. + To communicate via INTERNET, send E-mail to gdsbeta¹dce.austin.ibm.com. Remember to include a short descriptive subject heading. * Open Software Foundation and OSF are trademarks of the Open Software Foundation, Incorporated. * X/Open is a registered trademark of X/Open Company Limited. * PostScript is a registered trademark of Adobe Systems, Incorporated. (R) AIX and RISC System/6000 are registered trademarks of the IBM Corporation. Dean S. May LAN Systems Customer Readiness ====================================================================== >(U)93214. Yet another script to create man pages out of InfoExplorer The easy way is to create some man pages from the hypertext database. I don't know if xman handles the pre-formatted version of the man pages, but if so, this script should help a little. #|/bin/ksh # usage: make.man.pages # stores AIXv3 man pages as flat text in appropriate /usr/man/cat directory # # This is a script hacked from the advice and the semi script # in /usr/lpp/bos/bsdadm.tr file. # # Mickey_Coggins¹vnet.ibm.com 2 August 1993 catmanfunc() € NAMEPATH="/bin /usr/sbin /usr/ucb" # modify this to taste SECTION="1" if ÜÜ -n "$1" ðð ; then NAMEPATH="$1" fi if ÜÜ -n "$2" ðð ; then SECTION="$2" fi for p in $€NAMEPATHõ ; do for name in `ls "$€põ"` ; do if ÜÜ -x "$€põ/$€nameõ" ðð; then if ( man "$€SECTIONõ" "$€nameõ" >/usr/tmp/"$€nameõ" ) ; then mv /usr/tmp/"$€nameõ" /usr/man/cat"$€SECTIONõ"/"$€nameõ"."$€SECTIONõ" fi fi done done õ # # The sed command below has tabs in it, so don't cut and paste. # getLibraryNames() € mkdir /tmp/$1 ; cd /tmp/$1 dump -g /lib/$1 Ù sed -n -e 's/^Ü ð*Ü0-9ðÜ0-9ð*Ü ð*Ž(Ü^ .ðÜ^ ð*Ž)$/Ž1/p' Ù xargs touch catmanfunc /tmp/$1 cd /tmp ; rm -rf /tmp/$1 õ ÜÜ `whoami` |= "root" ðð && echo "You're not root, dude". && exit 1 echo This is going to take a long time. I recommend getting a cup of coffee, echo or perhaps lunch. Running... exec 2> /dev/null exec > /dev/null # build section 1 catmanfunc # build section 2 mkdir /tmp/syscalls; cd /tmp/syscalls touch `egrep '^Üa-zð' /lib/syscalls.exp Ù awk '€ print $1 õ' Ù tr ' ' 'Ž012'` catmanfunc /tmp/syscalls 2 cd /tmp rm -rf /tmp/syscalls getLibraryNames libc.a # build whatis database catman -w -- Mickey Coggins ====================================================================== >(I)93215. Euro-Unite| '93 Announcement and Call for Papers Euro-Unite| '93 Announcement and Call for Papers ------------------------------------------------- Following this note you will find an announcement and call for papers for Euro-Unite| '93. Euro-Unite| '93 will be held at the Zurich Research Laboratory in Switzerland from Tuesday to Thursday, October 12-14, followed by a Customer Day on Friday, October 15. Registration starts Monday night. Euro-Unite| is intended to supplement the US-based Unite| conferences, by providing a meeting place more local to European attendees, but IBM'ers are welcome from everywhere. The capacity of our auditorium at the lab is 80, so get your reservations in early| We will try to help with hotel reservations, but, please, feel free to make your own booking. The Customer Day on Friday, October 15 will be organized together with IBM Switzerland. We expect that it should be easy to prepare an interesting program for customers with the help of some of the experts coming to Euro-Unite. IBM Switzerland has a special budget which will allow to cover the additional expenses for those IBM speakers who are invited to stay on and to participate in the Customer Day. Ernst Rothauser For the Euro-Unite '93 Committee ############################################################################### Euro-Unite| '93 (Internal Meeting) Dates: October 12-14, 1993 Location: IBM Research Laboratory Zurich Deadline for Abstracts: September 1, 1993 Deadline for Attendees: September 1, 1993 Deadline for Papers: September 15, 1993 Euro-Unite| '93, 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: AIX Operating System and Application Programming Andrew File System & Distributed File System Distributed Computing Environment for all platforms System Administration Network Management Supporting Large Numbers of Workstations Writing MOTIF Applications User Interfaces (X, Motif, etc) Software Development Environments Software Development Experiences Experiences with AIX Tools for Basic Office & Administration Needs Potential of New Hardware, like Power PC, .. 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 own merit. The intention of Euro-Unite| is to provide and interchange ideas among programmers, engineers, and system administrators whose job involves Unix. Papers may be new material, work in progress, or interesting material previously published elsewhere. Presentations should be no longer than one hour in length. We may be forced to reduce requested schedules because of scheduling constraints. Please indicate the IBM security classification of the paper within the abstract, as well as the classification of the abstract itself. Presentation titles should not, in themselves, be classified. Euro-Unite| will be IBM Confidential, and the proceedings will be published as IBM Confidential material. We recognize that it may be impossible to abstract or describe certain talks in a non-confidential manner, but please attempt to do so. Authors will be notified of acceptance or rejection of their abstracts by September 8, 1993. IF THE ABSTRACT IS ACCEPTED, THE PAPER MUST BE SUBMITTED BY SEPTEMBER 30. Papers must be submitted as A4 camera-ready copy. Please include the title and the names of the authors on the first page of the paper rather than a separate page. Please leave a one inch margin at the top of each page for our use in preparing the proceedings. It is our intention to produce a proceedings containing all papers and other submitted materials which will be distributed to attendees as they arrive. Submit abstracts and proposals for roundtables to EUNITE at ZURICH. ######################################################################## Euro-Unite| '93 (Customer Day) Date: October 15, 1993 Location: IBM Switzerland Deadlines : as above The main differences as compared to the above Call for Papers are that the material to be presented must be unclassified at the time of presentation, and interesting for the intended audience. While the main purpose of the internal meeting is to foster the exchange of information, the Customer Day should offer only excellent technical papers to professional colleagues outside IBM. If you think you have a presentation which might qualify, submit it, and leave the pain of screening and coming up with a good program to us. Submit abstracts labelled 'Customer Day' to EUNITE at ZURICH. ######################################################################## We would also like to hear about potential key-note speakers who could be invited by us for one or both parts of Euro-Unite| '93 | ######################################################################## IBM Internal Use Only Euro-Unite| '93 - UNIX EUROPEAN INTERNAL TECHNICAL EXCHANGE Zurich, Switzerland October 12 through October 14th, 1993 Registration Application Form PLEASE RETURN THIS APPLICATION BY SEPTEMBER 1, 1993, TO EUNITE at ZURICH Do not send a hard copy application. Please fill in ALL the information requested, exactly as you'd like it to appear. Attendance is limited, incomplete forms may be rejected. Details of transportation from the airport to the laboratory will be posted at a later date. A confirmation that your application was received will be sent within one week. If you do not receive a confirmation, please send a note to EUNITE at ZURICH. Directions for filling out the form: Please leave the field names (with the colon, wherever it exists) intact at the beginning of the line, delete the underscores, and put your info on the line with the field name. We are going to use a software tool to parse the returned forms. Name: ___________________________________  Phone: (tie line)_____________________ First name as you wish it to appear on badge: _________________________ Job Description: ______________________________________________________ (vs. Position Title) E.g., AIX System Programmer (*not* Advisory Programmer) Userid: ____________ Node: ____________ Division: ______________ Location: _____________________________________ Internal Zip: _________________________________________________________ Manager: ______________________________________________________________ Manager's userid/node: ________/________ Has your manager approved this trip? ___ Hotel reservation needed(y/n): _ Arrival Date: __________ Number of Nights: __ Send to: EUNITE at ZURICH ====================================================================== >(I)93216. Writing deamons the easy way It's actually quite simple, if a bit cryptic. A good way I've found is to first write the program normally: it starts running in the foreground, performing initialization, allocating memory, writing messages to stdout, and writing errors to stderr. When it's time to become a deamon, the pdetach() subroutine is called. This subroutine (available by request) detaches the process from its tty and controlling group leader: it's really on its own now. It also does some other thoughtful things like forcing the cwd to be the root so filesystem commands like umount aren't affected by your daemon. I have a version written for PS/2 AIX 1.1. It should work as-is for AIX/3: I just haven't tried it myself but I've let some others have it and I haven't heard any complaints. You can request it as follows: REQUEST PDETACH PACKAGE FROM BEYODER AT BCRVM7 Brian Yoder ====================================================================== >(U)93217. Remote mksysb pitfalls and solutions From: op¹holmes.acc.Virginia.EDU (Olaf Pors) Subject: Re: mksysb on remote systems Organization: University of Virginia The remote mksysb scripts I have seen posted here contain a hidden danger. The scripts use the bosboot, mkinsttape and echo commands on the remote system (the one with the tape drive) to create the first 3 files on the boot tape. The scripts then perform the mksysb on the local system and pipe the result to the remote tape drive. There's no problem if the two machines have been upgraded to identical PTF levels. However, if, say, the remote machine is at 3.2.2 and the local machine is at 3.2.3, you may not be able to successfully restore from the tape later. When booted, the tape will create a 3.2.2 boot system (3.2.2 kernel, drivers, ODM, etc) in memory. The 3.2.3 files are then restored onto disk. During the final phase of the restore, the copying of /dev to disk, the merging of the ODM in RAM with the one on disk, etc, may fail. It's a risky game that quite often will work, and may fail when you need the tape most - when your machine is down and you HAVE to get it back up. I've made binary modifications to /usr/sbin/mkboot to allow the boot images to be created on the local machine. The images can then be FTP-ed over to a remote machine and dd-ed to tape. This is safe. If interested, get a copy of pub/rs6000/boottape.3.tar.Z from uvaarpa.Virginia.EDU via anonymous FTP. Luis, can this issue, and the related issues in pub/rs6000/rootvg.restores somehow be listed in the FAQ? People have been, and will continue to be burned by backup deficiencies unless they can find some FAQ information. Thanks. Olaf Pors Information Technology and Communications op¹Virginia.EDU 804-924-0633 ====================================================================== >(U)93218. List of available PTFs From: jsalter¹ibmpa.awdpa.ibm.com (James Salter) Subject: New List of AIX 3.2 PTFs and Abstracts as of 93/08/01 Organization: IBM PS Multimedia Mountain View, CA The latest list of AIX 3.2 PTFs as of 93/08/01 is available for anonymous ftp from the pub/ptfs directory of the machine: ibminet.awdpa.ibm.com (192.35.233.1) This list contains the AIX 3.2.4 PTFs. The following files are new or have changed: ptfs.all.930801 ptfs.all.930801.Z ptfs.abstracts.930805 (getting there, may take a couple of days) ptfs.abstracts.930805.Z (getting there, may take a couple of days) Please see the README for more information about the contents of these files, and how to extract the APAR information. Also available for anonymous ftp from this machine are the latest IBM product announcements and a list of OEM/Third Party Hardware for the RISC System/6000. WARNING: The tools in the pub/ptfs directory may be out-of-date. I haven't tested them in a couple of months, and some changes have occurred. DISCLAIMER: This information is provided as-is, with no warrenty or guarantee as to its correctness/timeliness. Always talk with your friendly-neighborhood IBM sales rep. for more/official info. APOLOGIES: As noticed by my long absense, I can't promise to get these out on a timely basis, but I will try my best. You know how it is, work gets in the way of doing what's really important in life. :-) For Internal IBM, you can pick these up as the PTFLIST package on AIXTOOLS tools disk, or from AFS: /afs/tcspa.ibm.com/u/jsalter/PTFs/lists/ptfs.* -- Jim Salter --- (415) 694-3827 T466-3827 IBM PS Multimedia 1055 Joaquin Rd. Mountain View, CA 94043 Internet/IBM Net: jsalter¹ibmpa.awdpa.ibm.com VNET/OV: JSALTER at ALMADEN -- How many times have you seen a Planner with a beeper? -- ====================================================================== >(I)93219. Sources of AIX information in Germany Use TOOLS SENDTO MUNIVM4 AIXTIOOLS AIXDOC GET AIXQUELL FILE to get a German document about AIX information sources. ====================================================================== >(I)93220. Soft graPHIGS Beta Program Welcome to the IBM Soft graPHIGS early availability program. The development team at IBM is excited about our newest graphics technology and wants to share it with you. This technology will provide competitive 3D graphics on all IBM RISC based platforms. Yes, that includes all of our present 2D configurations and the ones you don't have your hands on yet (ie. PowerPC). Our newer configurations should provide excellent price/performance for 3D applications. Soft graPHIGS is an implementation of IBM graPHIGS v2.2.4 where all rendering is done by software running on the RISC/6000 workstation. The final image is then copied to the video buffer. This allows full 3D function to be available on all display adapters. Additional Information 1. graPHIGS, PHIGS and GKS (via GKS compatibility option) are included in this package. PEX is not included but may be available at a future date (send a note if you are interested). 2. There is a separate program for OpenGL if you need information please send a note to gl-beta¹innerdoor.austin.ibm.com. 3. We are still benchmarking and optimizing soft graPHIGS. 4. Soft technology performance scales linearly with CPU performance. Soft running on a 580 performs |MUCH| faster than on a 520. Performance will continue to improve as faster processors (currently processor speeds double every 18 months) and hardware designed to accelerate soft graphics become available. Soft graphics is an important platform for most 3D applications. The price/performance will be very attractive on the low end as no 3D hardware is required and since performance scales with the cpu this will also hold for high end. Questions / Requests to participate in the Beta can be sent to GSBETA at KGNVMC (IBM VM network) gsbeta¹vnet.ibm.com (Internet) Marc Segre ====================================================================== >(U)93221. Getting the host name of the remote machine you are logged in from This script requieres the lsof utility that is available on most well stocked ftp servers. Thanks to Mickey. #|/bin/ksh PATH=$PATH:/usr/local/bin: PID=$$ PPID=$$ COMMAND="" while ÜÜ $COMMAND |= "rlogind" && "$COMMAND" |= "telnetd" && "$COMMAND" |= "rshd " ðð ; do PID=$PPID LINE=`ps -p $PID -F ppid=j -F comm=j Ù tail -1` LINE=`echo $LINE` PPID=$€LINE%% *õ COMMAND=$€LINE#* õ if ÜÜ $COMMAND = "swapper" ðð ; then exit 0 fi done case `basename $0` in *hostname) ADDR=`lsof -p $PID Ù grep TCP Ù tail -1 Ù sed -e 's/^.* //' -e 's/:..*$//'` ;; *client) ADDR=`lsof -p $PID Ù grep TCP Ù tail -1 Ù sed -e 's/^.*>//' -e 's/:..*$//'` ;; *) ;; esac ( host $ADDR 2>/dev/null ÙÙ echo $ADDR ) Ù sed "s/ ..*$//" exit 0 ====================================================================== ====================================================================== A question found on USENET: I have a serious hardware problem. A lot of programmes demand "press any key" but I've never seen a keyboard (neither of Unix machines nor of DOS or other ones) with an key on it. How can this Problem be solved? The key can be found on Swahili keyboards. On non-swahili keyboards you can simulate it by pressing , and at once.