<<< TEMBEL::OFFICE$DISK:[NOTES$LIBRARY]GENERAL.NOTE;1 >>> -< subjects that do not fit anywhere else! >- ================================================================================ Note 1.0 Welcome ... No replies BIGUN::KEOGH "I feel better than James Brown" 5 lines 6-AUG-1991 00:22 -------------------------------------------------------------------------------- Welcome to VAX NOTES This conference is for discussions relating to subjects that do not fit anywhere else!  ================================================================================ Note 2.0 HOSPITALITY_SUITE No replies VAXNET::BAKERK25 10 lines 19-AUG-1991 14:42 -------------------------------------------------------------------------------- A WELCOME IS EXTENDED TO ALL DELEGATES TO VISIT THE EMULEX HOSPITALITY SUITE IN THE BOARD ROOM OF THE PAN PACIFIC HOTEL AT THE REAR OF THE AOTEA CENTRE. ON DISPLAY WILL BE THE LATEST MASS STORAGE, TAPE AND COMMUNICATIONS EQUIPMENT TO ENHANCE YOUR DEC SYSTEM. COME IN AND DISCUSS THE BENEFITS OF THRID PARTY PERIPHERALS WHILST ENJOYING LIGHT REFRESHMENTS. REPRESENTATIVES FROM EMULEX CORP, AND EXCLUSIVE DISTRIBUTORS, ALLAW PLUS (AUSTRALIA) & DATACOM (NEW ZEALAND) WILL BE THERE TO ANSWER YOUR QUERIES. THE SUITE WILL BE OPEN FROM 10.00AM TO 5.00PM TUESDAY THROUGH THURSDAY. LOOK FORWARD TO SEEING YOU!!!  ================================================================================ Note 3.0 LA324 printers 3 replies TEMBEL::LANCASTERR1 "Robert (excuse the typing) Lancaster" 6 lines 19-AUG-1991 15:52 -------------------------------------------------------------------------------- I was wondering if there are people out there with LA324 printers. Any comments on them would be appreciated. ================================================================================ Note 3.1 LA324 printers 1 of 3 TEMBEL::NOSWORTHYD22 18 lines 20-AUG-1991 08:29 -< LA324 printers .. OK >- -------------------------------------------------------------------------------- We have a number of LA324 printers and find them to be more than satisfactory. We have used them in colour and graphics modes (out of spreadsheets) and have had no problems with functionality. We find the major problem associated with the paper feed and the lining up of the form feeds - not the easiest of DEC printers but after a bit of fiddling we have written a few user procedures to make sure the end user knows where to line up the stationery etc. The print quality is excellent although the ribbons (especially the coloured ones) are not particulalry cheap. Denis Nosworthy, South Western Sydney Area Health Service. ================================================================================ Note 3.2 LA324 printers 2 of 3 VAXNET::BEGGJ17 "Jeremy Begg" 12 lines 20-AUG-1991 15:48 -< LA324 is a very good printer >- -------------------------------------------------------------------------------- I have had an LA324 on my system for several months now, and find it a very worthy successor to the LA120, unlike the LA210. The print quality is very good and I have found it a reliable printer. On the other hand, the usage has not been heavy. As far as users are converned, they like the ease of swapping between tractor feed and sheet feed (once they are shown how :-) Jeremy Begg VSM Software Services jeremy@vsm.com.au ================================================================================ Note 3.3 LA324 printers 3 of 3 TEMBEL::BAKERB27 "Bruce Baker, Dow Chemical (Aust) Ltd" 19 lines 20-AUG-1991 18:12 -< Much disatisfaction with LA324s >- -------------------------------------------------------------------------------- I have experience with 3 LA324s. One was replaced in our payroll office due to its inability to handle the (excessively) heavy card stock of the paycards. The replacement was a Seikosha with a similar paper path, but a slightly better design on the exit. The Seikosha doesn't catch the leading edge or fanfold like the LA324 did. But we thought the task we asked of it was unreasonable anyway. The other two LA324s are resulting in much abuse from their users. They are used for printing 5 part purchase order forms. They were purchased because of the zero bar tear off feature. The forms cost about $1 each so we thought much money would be saved. We actually waste more forms now because of the jams. Our Field service engineer has measured the forms and checked the physical setup of the printers. It is all within spec. The latest request was to swap out one of the printers and give DEC a box of the forms to go away and play with on the printer. The users want their LA36s back. We will be extremely unlikely to purchase further LA324s.  ================================================================================ Note 4.0 MicroVax 2000 Backup Problem 9 replies TEMBEL::SUTTONT13 9 lines 20-AUG-1991 08:29 -------------------------------------------------------------------------------- We have a microVax 2000 with 6Mb memory, 2 RD54 disks and a TK50 tape. When doing backups at night even though the CPU is only 20-40% utilised it is not possible to do any othe work on the machine as response time is so slow. A full tape takes ~60 minutes to write. All the appropriate SYSGEN & UAF parameters are set according to the manual. Question: Is there anything that can be done to increase response time while backup is running or is this just a limitation of the MicroVax hardware. ================================================================================ Note 4.1 MicroVax 2000 Backup Problem 1 of 9 TEMBEL::LANCASTERR1 "Robert (excuse the typing) Lancaster" 10 lines 20-AUG-1991 09:33 -< Backup is too memory hungry >- -------------------------------------------------------------------------------- Have you checked to see how much memory is used. If we run two backups during a live user session on our 3500 response time becomes un acceptable. The only solution I know is to reduce the UAF's memory requirements to a reasonable level for your system. The parameters in the manual are written by the writers of backup and they care little about other users just fast backups!! ================================================================================ Note 4.2 MicroVax 2000 Backup Problem 2 of 9 TEMBEL::SOMMERVILB19 "Brian Sommerville - BT Aust." 7 lines 20-AUG-1991 11:13 -< A lower priority? >- -------------------------------------------------------------------------------- Is the elapsed time of the backup important? If not how about lowering the priority of the backup job? cheers brian ================================================================================ Note 4.3 MicroVax 2000 Backup Problem 3 of 9 VAXNET::GARNERR30 "Whale Oil Beef Hooked" 5 lines 20-AUG-1991 13:07 -< Too late ... >- -------------------------------------------------------------------------------- Keith Walls' talk this morning covered how to "de-tune" backup to reduce its resource consumption. The main thing is to reduce WSQUOTA for the backup process. I gather he has submitted a paper covering his talk this morning, which will appear in the proceedings later this year. Or, you can try tracking him down through the network Computer Services people. ================================================================================ Note 4.4 MicroVax 2000 Backup Problem 4 of 9 TEMBEL::SUTTONT13 6 lines 20-AUG-1991 15:52 -< Lower priority doesnt work. >- -------------------------------------------------------------------------------- Altering the priority of either backup job or user process has no noticeable effect (have had backup at priority 4 & user @ priority 10!!!) CPU time is approx 12 mins Elapsed time is approx 1hour. ================================================================================ Note 4.5 MicroVax 2000 Backup Problem 5 of 9 TEMBEL::HAWLEYD13 "Tektronix EDP Manager" 11 lines 22-AUG-1991 09:11 -< Fragmented disk? >- -------------------------------------------------------------------------------- I would be interested in how fragmented your disk is that you are backing up. Our experience is that RD drives can suffer badly when they are fragmented. Note also that for the MV2000 the disk and tape controller is effectively built in to the motherboard (it's a modified SCSI), so it is conceivable that heavy disk/tape operation saps CPU power from other users. You need to drastically reduce the disk/tape overhead on this machine, thus the need for defragmentation. RSVP ================================================================================ Note 4.6 MicroVax 2000 Backup Problem 6 of 9 TEMBEL::WALLACEA21 12 lines 22-AUG-1991 10:16 -< Problem is specific to the 2000. >- -------------------------------------------------------------------------------- We had a MicroVAX 2000, RD54, TK50 on loan while waiting for our new system and had the same problem with backups. It seemed to be a problem specific to the hardware combination, since a MicroVAX II with RD53's and TK50 has no problem running Backup while normal use continues (preferably with /NOCRC). However, the MicroVAX 2000 dies while running backup to the TK50. I found it much faster to backup a group of files to a disk saveset, then COPY the saveset to tape, delete the saveset, then repeat as necessary. This is a nuisance, but results were much better. ================================================================================ Note 4.7 MicroVax 2000 Backup Problem 7 of 9 VAXNET::GARNERR30 "Whale Oil Beef Hooked" 10 lines 22-AUG-1991 12:11 -< Throttle backup >- -------------------------------------------------------------------------------- Keith Walls' answer to this was to detune backup by decreasing the DIOLM of the backup process. Otherwise (and this is why lowering priority doesn't work), each time BACKUP gets to the CPU, it queues enough I/O to saturate the I/O paths (MV 2000 doesn't have a bus worth talking about) and annihilate performance on the system. Restrict backup to having a small number of I/Os outstanding and the problem reduces. This of course means that the backup takes longer, but you can't have everything. You can always put the poor 2000 out of its misery :-) ================================================================================ Note 4.8 MicroVax 2000 Backup Problem 8 of 9 TEMBEL::MCGILLC8 12 lines 22-AUG-1991 15:53 -------------------------------------------------------------------------------- I would strongly recommend *AGAINST* copying the already created saveset to tape via the COPY command. All of the error checking and retry code in BACKUP is not present in COPY, and the copy to the tape is when you need it, not when you're saving to disk ! You are gojng to lose data, it is just a question of when. DON'T DO IT ! Detune BACKUP by reducing WSQUOTA and FILLM, as documented in the VMS V5.2 New Features manual (also reprinted in the VMS V5.4 New Features manual). Also, lowering priority is not going to do much since it is probably I/O bound anyway, and lowering priority is mostly a useless exercise on a system that is not 100% CPU bound (not *totally*, but mostly). ================================================================================ Note 4.9 MicroVax 2000 Backup Problem 9 of 9 TEMBEL::WALLACEA21 3 lines 23-AUG-1991 12:19 -< Copying savesets >- -------------------------------------------------------------------------------- Copy was used to make the system useable. I'll take the chance of losing data if it makes the system useable.  ================================================================================ Note 5.0 Decserver 90's 1 reply TEMBEL::LANCASTERR1 "Robert (excuse the typing) Lancaster" 3 lines 20-AUG-1991 10:46 -------------------------------------------------------------------------------- Are the decserver 90's as bad as the one's here at DECUS Should Virtual terminals be set up here for some continuity of thought?? ================================================================================ Note 5.1 Decserver 90's 1 of 1 TEMBEL::MANDENOG29 "Graham Mandeno - ALCAN" 3 lines 20-AUG-1991 10:50 -< VT's pleeeease! >- -------------------------------------------------------------------------------- 1. They're certainly putting me off! 2. Bloody good idea!!  ================================================================================ Note 6.0 X.29 Access to your home machine via ULTRIX No replies VAXNET::NASHA20 26 lines 20-AUG-1991 11:37 -------------------------------------------------------------------------------- An additional method of obtaining X.29 access to your home machine has been provided via the new ULTRIX X.25 software. If you wish to call home: at the local prompt on the terminal server type: CONN ULTRIX_X29 login as x25 with password ultrix (note this MUST be in lower case) to connect via X.29 x29login dte-number to run up a test demo in Australia use: x29login 050527532100233 Assistance or answers to questions can be obtained from the X.25 for ULTRIX demo area next to the Networking booth.  ================================================================================ Note 7.0 vt1200 Reliability 5 replies TEMBEL::LINDSAYP21 10 lines 20-AUG-1991 11:50 -------------------------------------------------------------------------------- Does anyone else experience problems with Vt1200 crashing unpredictably?. We have just had our firmware upgraded to v2.2 but this has not helped the problem significantly. Has anyone had any response from DEC on what they are doing to fix the problem? In addition, has anyone got a fix for the slow response of the "hold screen" key on anything running decwindows (DECTERM), eg PC's, vt1200's workstations etc. ================================================================================ Note 7.1 vt1200 Reliability 1 of 5 VAXNET::SARGENTD25 16 lines 20-AUG-1991 15:16 -< VT1200 Unreliability >- -------------------------------------------------------------------------------- We are running VT1000/1200s at various level of firmware. V1.2 runs most of the time if you don't mind s l o w responses. V2.0 runs a lot faster but has the crashing problem you mentioned. We thought V2.2 had solved the problem ( we only have about three at this level) but if what you say is true then we are in the same boat. We have had 2.2 installed for only a few weeks so maybe we haven't had time to gather enough stats. I use my personal VT1200 for Decwindows ONLY and never experience any problems, goes like a charm all the time. Sorry I couldn't actually help but at least you know you're not alone. Daryl Sargent ACTEW ================================================================================ Note 7.2 vt1200 Reliability 2 of 5 TEMBEL::STANLEYBOP20 18 lines 21-AUG-1991 10:50 -< vt1000 crashes >- -------------------------------------------------------------------------------- We are currently using a VT1000/1200 for DECwrite and have gone through the series of firmware revision to v2.2. The unit still crashes out completely or locks up. The "less than optimal performance" occurs a number of times each day, when the unit is use. The only warning the user gets is incredible slow performance just prior to death. Sometimes its possible to save at this point sometimes not. Needless to say the post crash recover period is long enough for several cups of coffee. Each crash probably costs the user a good 30minutes of lost productivity. I can offer no solution... except get a NCD. Paul Stanley-Boden NZ Wool Board ================================================================================ Note 7.3 vt1200 Reliability 3 of 5 TEMBEL::SHERRIFFJ3 11 lines 21-AUG-1991 10:51 -< VT1200 solution >- -------------------------------------------------------------------------------- You are not alone with VT1200 hangs and crashes. We experience most of our problems when running DECwrite. ROM upgrades have only been of limited success. Both ourselves and Digital have spent a lot of time trying to sort out the problems but (by mutual agreement) we have now reached the end of the road. Our only solution is to replace the VT1200s. I suggest you contact your account manager. John Sherriff ================================================================================ Note 7.4 vt1200 Reliability 4 of 5 TEMBEL::SMITHD28 "Danny Smith, University of Queensland" 21 lines 21-AUG-1991 20:13 -< no answers, just different problems >- -------------------------------------------------------------------------------- I have been working with a VT1200 for some time now to try and fix some problems for another department. At the previous rev levels of the firmware, we experienced crashes which were attributable to low memory situations. If you got to less than 200K free memory, you could expect a crash. We also experienced crashes in V1.1 of the firmware. Another problem was in the Postscript refreshing. A "pre-release" version of the ROMs fixed a number of these. The postscript one is fixed, and the terminal will not acceot new connections when it gets low on memory. However, we are now getting random crashes. We haven't received our V2.2 ROMs yet, but it sounds like they won't help. cheers, dfs... p.s. I personally have an NCD on my desk. We have been looking at all sorts of X terminals - contact if you are interested in a chat. ================================================================================ Note 7.5 vt1200 Reliability 5 of 5 TEMBEL::HAWLEYD13 "Tektronix EDP Manager" 1 line 22-AUG-1991 09:14 -< See Tektronix! >- -------------------------------------------------------------------------------- Have a read of the Tektronix X-station write-up in the latest ON$DECK.