1 INFO-VAX	Wed, 17 Aug 2005	Volume 2005 : Issue 457       Contents:* Re: $SHOW DEVICE/FILES enhancement request* Re: $SHOW DEVICE/FILES enhancement request/ Re: Changing Uppercase filenames into Lowercase - Re: Command to find new drives from VMS Level % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set   Re: Investigating ACCVIO problem Re: Is OVMS going Bangalore?7 Re: Killing a process that has allocated the tape drive ) Re: OpenVMS Integrity V8.2-1 New Features ) Re: OpenVMS Integrity V8.2-1 New Features ) Re: OpenVMS Integrity V8.2-1 New Features  Oracle HTTP Server anyone?0 Re: Print Queue in "starting" state  --  cause??  Re: Replacement for VT terminals  Re: Replacement for VT terminals  Re: Replacement for VT terminals  Re: Replacement for VT terminals  Re: Replacement for VT terminals  Re: Replacement for VT terminals  Re: Replacement for VT terminals  RE: Replacement for VT terminals  Re: Replacement for VT terminals  Re: Replacement for VT terminals  Re: Replacement for VT terminals Re: SAMBA for VMS  Re: SAMBA for VMS  Re: SAMBA for VMS  Re: SAMBA for VMS  Re: SAMBA for VMS  Re: SAMBA for VMS ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!)  simh define/attach printer Re: simh define/attach printer Re: simh define/attach printer Re: simh define/attach printer Re: Squid for VMS # Re: The Educational License Program # Re: The Educational License Program 3 Was -->  Print Queue in "starting" state -- cause?? 3 Was -->  Print Queue in "starting" state -- cause?? 7 Re: Was -->  Print Queue in "starting" state -- cause?? 6 Re: Was --> Print Queue in "starting" state -- cause??6 Re: Was --> Print Queue in "starting" state -- cause??  F ----------------------------------------------------------------------    Date: 16 Aug 2005 16:25:10 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 3 Subject: Re: $SHOW DEVICE/FILES enhancement request 3 Message-ID: <3taRx5zqaKpR@eisner.encompasserve.org>   c In article <XTfAqrm8Djq9@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:  >>  H >>    We had lots of system disks.  IIRC homgeneous clustering means oneC >>    SYSUAF, one RIGHTSLIST, ..., no matter how many system disks.  > C > But the system I outlined was homogeneous (under that definition) D > with certain users only allowed to log into certain systems.  That@ > restriction would be defeated if OPER were not required to use	 > SYSMAN.   H    In a homogeneous system, how are you implementing that?  Via sylogin?9    Via RIGHTSLIST?  SYSMAN should not violate the latter.    ------------------------------    Date: 16 Aug 2005 17:40:22 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) 3 Subject: Re: $SHOW DEVICE/FILES enhancement request 3 Message-ID: <YS1wmd9ghfTb@eisner.encompasserve.org>   q In article <3taRx5zqaKpR@eisner.encompasserve.org>, koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: e > In article <XTfAqrm8Djq9@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:  >>> I >>>    We had lots of system disks.  IIRC homgeneous clustering means one D >>>    SYSUAF, one RIGHTSLIST, ..., no matter how many system disks. >>  D >> But the system I outlined was homogeneous (under that definition)E >> with certain users only allowed to log into certain systems.  That A >> restriction would be defeated if OPER were not required to use 
 >> SYSMAN. > J >    In a homogeneous system, how are you implementing that?  Via sylogin?  G All the terminals on system A are Local.  All the terminals on system B G are Dialup.  Some users are not allowed to log in via certain types via  the Access fields in SYSUAF.   ------------------------------  % Date: Tue, 16 Aug 2005 16:52:02 -0700 ! From: Fred Bach <music@triumf.ca> 8 Subject: Re: Changing Uppercase filenames into Lowercase( Message-ID: <43027C22.1060607@triumf.ca>   Aaron,  7   Not a bad idea when it's ready.  I don't like to post 9   poor code, unreadable or uncommented code, or code with :   known bugs.  Before today, MAKELOWER.COM worked, but had   all four above problems.  9   I made some progress today on tidying up and commenting 4   MAKELOWER.COM so that it doesn't, when changing an:   uppercase filename to a lowercase filename, read the new+   lowercase filename as the next hit in the 0   foundfile = f$search(filespec,1) command line.  9   Actually it DOES read the new filename (!), and so that :   scenario had to be trapped out.  I got myself into a few=   endless loops today that I had to CONTROL-Y out of, but the ?   33rd revision seems to work fine.  I'll wait a while, and put A   it in use here at the lab before posting it to dcl.openvms.org. @   I've seen some badly written code posted there, and complained>   about it, so I don't want to be guilty of my own complaints.?   (Frankly I think I could tidy up much of that code.  Not that *   the code below is any great example....)  1   Below is the current test copy of MAKELOWER.COM      .. fred bach  music@triumf.ca     % $! MAKELOWER.COM   Beta test version. = $! make all filenames lowercase in current working directory. 6 $! Created by F.W. Bach, TRIUMF Operations 09-AUG-2005< $! Based on a command procedure by Willem Grooters which was= $! posted on Friday June 18 2004 @ 03:42AM EDT ("MAKEUP.COM") < $! http://dcl.openvms.org/stories.php?story=04/06/18/6280218 $!F $! NOTE: This command procedure works when your DCL parse style is set$ $!       to Traditional, i.e., where5 $!                           RENAME FRED.TMP fred.tmp G $!       does NOT result in a lowercase fred.tmp file in the directory.  $!K $!       To make the above command work, that is to make the RENAME command F $!       recognize and produce lowercase filenames right from your DCLI $!       command line WITHOUT using the ampersand ("&")  technique below, 8 $!       you will need to set your parse style this way: $!2 $!                SET PROCESS/PARSE_STYLE=EXTENDED $!N $!       To restore the normal uppercasing of the whole, unquoted, DCL command $!       line:5 $!                SET PROCESS/PARSE_STYLE=TRADITIONAL  $!* $!       See HELP SET PROCESS /PARSE_STYLE $!L $! 12-AUG-2005 fwb. Add -Y arg for user to do all files without confirmationM $!                  For -Y, shift all cmd line args down one, for future use. M $! 16-AUG-2005 fwb. Catch & prevent looping on file already renamed to lower. - $!                  Show Foundfile each pass. E $!                  Add error message if no files found matching arg. ! $!                  Add comments.  $! $!; $! The first arg, P1, can be either a file name or pattern, = $! or it could be -y or -Y to override the confirm on rename. ; $! In this latter case, the -y is dealt with, and all other 5 $! args on the command line are pulled forward by one = $! (i.e., p2 becomes p1, p3 becomes p2, p4 becomes p3, etc.). < $! This will eventually allow us the ability to specify upto< $! 6 other file names/patterns via the other args, some day. $! $! if p1 is -y or -Y, D $! then P2 is the filespec, which may include wildcards, if missing,A $!                     defaults to *.*;* in the current directory  $! $! Will not rename directories. 4 $! Requires DELETE access on files (due to 'rename')# $! (THIS IS NOT CHECKED BEFOREHAND) / $!---------------------------------------------  $! $ ver = f$verify(0)  $ say = "write sys$output"
 $ set noon $ , $ if f$edit(p1,"UPCASE,COLLAPSE") .eqs. "-Y" $  then  $   no_confirm = "TRUE" @ $! since p1 was used up, walk forward all the arguments one step $   p1 = p2  ! used now  $   p2 = p3  ! future use  $   p3 = p4  ! future use  $   p4 = p5  ! future use  $   p5 = p6  ! future use  $   p6 = p7  ! future use  $   p7 = p8  ! future use  $   p8 = ""  $  else  $   no_confirm = "FALSE"8 $   say "Confirmation will be requested on all RENAMEs." $ endif  $ searchspec = P1 2 $ if searchspec .eqs. "" then searchspec = "*.*;*" $!$ $! Loop through all files until done $!0 $ old_foundfile = "" !to prevent endless looping" $ pass = 0           !pass counterP $ searchspec = f$edit(searchspec,"lowercase,trim") !help prevent endless looping $loop: $ foundfile=""" $ foundfile=f$search(searchspec,1)* $ if foundfile .eqs. "" then goto end_loop $ show symbol foundfile  $!J $! prevent endless looping on identical filename, filetype, fileversion...5 $ if foundfile .eqs. old_foundfile then goto end_loop  $!I $! now we can save the foundfile as old_foundfile for use in next loop...  $ old_foundfile = foundfile  $!! $! NO case change if directory... < $ if f$file_attributes(foundfile,"DIRECTORY") then goto loop $!( $ filedev =f$parse(foundfile,,,"DEVICE")+ $ filepath=f$parse(foundfile,,,"DIRECTORY") & $ filename=f$parse(foundfile,,,"NAME")& $ filetype=f$parse(foundfile,,,"TYPE")) $ filevers=f$parse(foundfile,,,"VERSION")  $!! $! Now lowercase name and type... * $ lowername = f$edit(filename,"LOWERCASE")* $ lowertype = f$edit(filetype,"LOWERCASE") $!( $! rename the original names to LOWER... $ old_filename = foundfile> $ new_filename = filedev+filepath+lowername+lowertype+filevers $!8 $! *** Check first if this filename is ALREADY lowercase+ $! *** and just put out a message if it is.  $!$ $ if old_filename .eqs. new_filename $  then > $!   say "No need to rename ",old_filename," to ",new_filename
 $   goto loop  $ endif ' $ say old_filename," ==> ",new_filename I $ rename = "RENAME" ! in case it was redefined in login.com or define.com  $! ***D $! ***  Use of the AMPERSAND symbol (&) prevents DCL uppercasing theB $! ***  contents of the symbol new_filename, since the translationD $! ***  of the symbol is done AFTER DCL interprets the command line. $! *** $ if no_confirm .eqs. "TRUE" $  then 4 $   rename/log/noconfirm &old_filename &new_filename $  else 2 $   rename/log/confirm &old_filename &new_filename $ endif  $! $ pass = pass + 1  $ goto loop  $!
 $end_loop: $ if pass .eq. 0 $  then J $   say "Sorry. No files matched pattern ''searchspec' to make lowercase." $ endif  $ ver = f$verify('ver')  $ exit       Alphaman wrote:    > Fred Bach wrote: >  > % >>  But am I missing something easy?  ! >>  .. fred bach  music@triumf.ca  >  > H > Uhm, the only thing I can think of that is missing right now is these - > procedures being posted on dcl.openvms.org!  >  > Feel free to share them! >  > Best,  > Aaron    ------------------------------  + Date: Tue, 16 Aug 2005 20:31:14 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)6 Subject: Re: Command to find new drives from VMS Level$ Message-ID: <ddtiei$7im$1@online.de>  B In article <1124194722.104190.89390@g43g2000cwa.googlegroups.com>,. "Shawn M." <shawnm1964@sbcglobal.net> writes:   H > I am having a brain fart.  I can't remember the command that I can runC > from the OpenVMS level of a Alpha Server running 7.2-1 which will C > search the bus(s) and find disk drives.  Cany anyone lend a hand.   I If you ever are lucky enough to have the joy of VAX (hey, there's a book   title there!), then it is    $  MC SYSGEN AUTOCONFIGURE ALL     ------------------------------    Date: 16 Aug 2005 10:48:22 -0700( From: "Chris Allen" <ca.allen@gmail.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124214502.786894.108860@g49g2000cwa.googlegroups.com>    > Brad Hamilton wrote: > > L > > I looked at the snippet of code that you posted earlier - is it possibleK > > that "BACK" has been defined (symbol?) as "BACKUP/DENSITY=<mumble>"?  I ' > > realize this is a long shot, but...  >  > Chris Allen wrote:H > I doubt it but I'll check tomorrow and let you know.  Good suggestion. > You never know right?     ( Thanks but nope, no BACK symbol defined.   ------------------------------  % Date: Tue, 16 Aug 2005 14:16:07 -0400 - From: William Webb <william.w.webb@gmail.com> . Subject: Re: Help Needed: Tape Backup Save Set6 Message-ID: <8660a3a105081611165ad0238@mail.gmail.com>  F On 15 Aug 2005 16:48:51 -0700, Chris Allen <ca.allen@gmail.com> wrote:F > One other thing... I'm getting this error everytime I backup.  "DoesE > not support specified density - default used"  I'm not specifying a E > density in my backup .com file.  HELP/BACKUP says that if it is not H > specified then the current density will be used.  However even after IF > write a backup with my script I get the error repeatedly even thoughE > the default density was used the last time (since it told me it was F > using the default density).  My drive is a TZ89, the help suggests II > put in /DENSITY=3DTK89, which is fine but it also mentions that it must H > be paired with the /REWIND qualifier.  What if I want to append to the > tape?  >=20 >=20  I I haven't used BACKUP/DENSITY=3D since I was backing up to 9-track tapes.   H IMHO, it's more important that you init tapes /MEDIA_FORMAT=3DCOMPACTION0 and include that in your BACKUP command as well.  @ You are on an Alpha and running 7.2 or later, as the online helpA indicates that's the architecture and minimum version of VMS that   /DENSITY=3DTK89 is supported on?   BACKUP  
   /DENSITY           /DENSITY=3DN        Output Save-Set Qualifier  C      Specifies the recording density of the output magnetic tape in B      bits per inch (bits/in). Use a value that is supported by the      magnetic tape drive.   F      If you do not specify the /DENSITY qualifier, the default density@      is the current density of the magnetic tape drive. You mustA      specify the output save-set qualifier /REWIND with /DENSITY.         Format   =        input-specifier output-save-set-spec/DENSITY=3Dkeyword   ?    The densities supported for tapes and disks are shown in the       following table.         Table 1 Keywords for Tapes         Keyword        Meaning   #      DEFAULT        Default density 0      800            NRZI 800 bits per inch (BPI)      1600           PE 1600 BPI        6250           GRC 6250 BPI*      3480           IBM 3480 HPC 39872 BPI'      3490E          IBM 3480 compressed %      833            DLT TK50: 833 BPI %      TK50           DLT TK50: 833 BPI &      TK70           DLT TK70: 1250 BPI,      6250           RV80 6250 BPI EQUIVALENT@            NOTE: Only the symbols listed above are understood byE       TMSCP/TUDRIVER code prior to OpenVMS Version 7.2. The remaining >      values in this table are supported only on Alpha systems.0      TK85           DLT Tx85: 10625 BPI-Cmpt III0      TK86           DLT Tx86: 10626 BPI-Cmpt III0      TK87           DLT Tx87: 62500 BPI-Cmpt III4      TK88           DLT Tx88: (Quantum 4000)-Cmpt IV4      TK89           DLT Tx89: (Quantum 7000)-Cmpt IV:      QIC            All QIC drives are drive-settable only!      8200           Exa-Byte 8200 !      8500           Exa-Byte 8500 -      DDS1           Digital Data Storage 1-2G -      DDS2           Digital Data Storage 2-4G 0      DDS3           Digital Data Storage 3-8-10G*      DDS4           Digital Data Storage 43      AIT1           Sony Advanced Intelligent Tapes   B      The value that you specify must be supported by your magneticF      tape hardware. If you omit this qualifier, the default density is2      the current density on the output tape drive.  A      The /DENSITY qualifier is incompatible with the output save- B      set qualifier /NOREWIND. You must specify the output save-setA      qualifier /REWIND to initialize the magnetic tape when using >      the /DENSITY qualifier. When you specify /DENSITY/REWIND,B      BACKUP rewinds the tape to the beginning-of-tape. Then BACKUPF      initializes the tape with the new density, removing access to all.      data that previously resided on the tape.   WWWebb   --=20 C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  % Date: Tue, 16 Aug 2005 13:35:52 -0600 + From: Mark Berryman <mark@theberrymans.com> . Subject: Re: Help Needed: Tape Backup Save Set% Message-ID: <4301dda8$1@mvb.saic.com>    Steven M. Schweda wrote:8 > From: Brad Hamilton <brMadAhamPiltSon@coMmcaAstP.neSt> > ' >>>>$backup/list (tape device)/save_set & >>>>                         ^^^^^^^^^ >>> K >>>  If anyone ever finds a case where /SAVE_SET is actually required for a + >>>tape device, please provide the details.  >>J >>I remember that back in the VMS 5.* days, this used to be a requirement. >  > 9 >    Those are details?  In any case, you mean like this?  > . > WIMP $ write sys$output f$getsyi( "VERSION") > V5.4 > " > WIMP $ backup /noass /list mua0: > Listing of save set(s) > , > %MOUNT-I-WRITELOCK, volume is write locked1 > %MOUNT-I-MOUNTED, WUSS02 mounted on _WIMP$MUA0: E > %BACKUP-W-NOT1STVOL, MUA0:[000000].; is not the start of a save set    [much deleted]  J >    And I'm still waiting for a counter-example on /SAVE_SET, and I still > won't be holding my breath.   D Well, I was going to pass on this but now you've gotten demanding...  9 $ BACKUP filespec node::tape_device:filename.ext/save_set   I requires the /save_set switch.  I use this on both 7.3-2 and 8.2 systems.   
 Mark Berryman    ------------------------------    Date: 16 Aug 2005 13:12:08 -0700( From: "Chris Allen" <ca.allen@gmail.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124223128.777128.239430@g47g2000cwa.googlegroups.com>    William Webb wrote:  > I > I haven't used BACKUP/DENSITY= since I was backing up to 9-track tapes.  > H > IMHO, it's more important that you init tapes /MEDIA_FORMAT=COMPACTION2 > and include that in your BACKUP command as well. > B > You are on an Alpha and running 7.2 or later, as the online helpC > indicates that's the architecture and minimum version of VMS that   > /DENSITY=TK89 is supported on?      G Well I think the problem is I have DLT IV 40/80 tapes and the TZ89 is a G 35/70 drive.  Pretty stupid I know, but that's how things go sometimes.    Is it safe to backup like this?   ------------------------------  + Date: Tue, 16 Aug 2005 15:38:42 -0500 (CDT) * From: sms@antinode.org (Steven M. Schweda). Subject: Re: Help Needed: Tape Backup Save Set2 Message-ID: <05081615384287_20A0026A@antinode.org>  + From: Mark Berryman <mark@theberrymans.com>   L > >    And I'm still waiting for a counter-example on /SAVE_SET, and I still > > won't be holding my breath.  > F > Well, I was going to pass on this but now you've gotten demanding... > ; > $ BACKUP filespec node::tape_device:filename.ext/save_set  > K > requires the /save_set switch.  I use this on both 7.3-2 and 8.2 systems.   F    That's a network device.  You just _think_ that it's a tape device.      SMS.    ------------------------------    Date: 16 Aug 2005 16:01:11 -0700$ From: "AEF" <spamsink2001@yahoo.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124231099.797022.166740@g49g2000cwa.googlegroups.com>    Wayne Sewell wrote: ' > >From: "AEF" <spamsink2001@yahoo.com>  > >X-Newsgroups: comp.os.vms1 > >Subject: Re: Help Needed: Tape Backup Save Set # > >Date: 10 Aug 2005 19:52:55 -0700 ) > >Organization: http://groups.google.com  > >Lines: 27 >  > >  > >Z wrote:  > >> William Webb wrote:
 > >> > If you + > >> > MOUNT/FOREIGN tape_device tape_label  > >> > You can  > >> > BACKUP/LIST tape_device:* > >>C > >> If you're going to use BACKUP, let VMS mount the tape for you.  > > J > >Uh, on a v5.4-1 system I had trouble using BACKUP to mount a tape. If II > >put in a tape that was not the first save set volume it would screw up A > >with funny characters reported as the label. Using an explicit G > >MOUNT/FOR made everything work fine. Ever since then I tend to do an B > >explicit MOUNT first, except with standalone backup, of course! > >  >  > O > This appears to be historical residue from the previous millenium.  I was not + > able to reproduce this behavior on 7.3-2.  > F > In the following example, tape DLT038 is a continuation of a saveset   [example omitted]    > [...]    > P > Sure it got a warning message about not being at the beginning of the saveset,J > but it certainly had no problems finding the label or mounting the tape.    C Another reason I like to MOUNT before I BACKUP is that I often have D very annoying and time-consuming problems with tape drives. Doing anD explicit MOUNT helps me determine just where the problem is. WaitingF for the load light to stop blinking before I issue any commands at allE also helps me determine what is causing a problem. If I just pop in a F blank tape and do a BACKUP ... /REWIND and there is trouble it is more difficult to troubleshoot.  F Additionally, anything that *might* cause trouble, like skipping MOUNTC when reading the 2nd tape volume, I prefer to avoid just in case it  causes a problem.   G Additionally**2, as lazy as I sometimes can be, it never bothered me to C have to do a MOUNT/FOR before running BACKUP. Eventually, I did get E into the habit of skipping the explicit MOUNT, only to have to wander , yet again through tape-drive headache space.  B Remember: I am the author of "I Lost It with the Tape Drive v1.0".   AEF    ------------------------------    Date: 16 Aug 2005 15:58:01 -0700$ From: "AEF" <spamsink2001@yahoo.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124233081.009641.191750@f14g2000cwb.googlegroups.com>    Wayne Sewell wrote: ' > >From: "AEF" <spamsink2001@yahoo.com>  > >X-Newsgroups: comp.os.vms1 > >Subject: Re: Help Needed: Tape Backup Save Set # > >Date: 10 Aug 2005 19:52:55 -0700 ) > >Organization: http://groups.google.com  > >Lines: 27 >  > >  > >Z wrote:  > >> William Webb wrote:
 > >> > If you + > >> > MOUNT/FOREIGN tape_device tape_label  > >> > You can  > >> > BACKUP/LIST tape_device:* > >>C > >> If you're going to use BACKUP, let VMS mount the tape for you.  > > J > >Uh, on a v5.4-1 system I had trouble using BACKUP to mount a tape. If II > >put in a tape that was not the first save set volume it would screw up A > >with funny characters reported as the label. Using an explicit G > >MOUNT/FOR made everything work fine. Ever since then I tend to do an B > >explicit MOUNT first, except with standalone backup, of course! > >  >  > O > This appears to be historical residue from the previous millenium.  I was not + > able to reproduce this behavior on 7.3-2.  > F > In the following example, tape DLT038 is a continuation of a saveset   [example omitted]    > [...]    > P > Sure it got a warning message about not being at the beginning of the saveset,J > but it certainly had no problems finding the label or mounting the tape.    C Another reason I like to MOUNT before I BACKUP is that I often have D very annoying and time-consuming problems with tape drives. Doing anD explicit MOUNT helps me determine just where the problem is. WaitingF for the load light to stop blinking before I issue any commands at allE also helps me determine what is causing a problem. If I just pop in a F blank tape and do a BACKUP ... /REWIND and there is trouble it is more difficult to troubleshoot.  F Additionally, anything that *might* cause trouble, like skipping MOUNTC when reading the 2nd tape volume, I prefer to avoid just in case it  causes a problem.   G Additionally**2, as lazy as I sometimes can be, it never bothered me to C have to do a MOUNT/FOR before running BACKUP. Eventually, I did get E into the habit of skipping the explicit MOUNT, only to have to wander , yet again through tape-drive headache space.  B Remember: I am the author of "I Lost It with the Tape Drive v1.0".   AEF    ------------------------------  % Date: Tue, 16 Aug 2005 20:25:21 -0500 ( From: Wayne Sewell <wayne@tachysoft.com>. Subject: Re: Help Needed: Tape Backup Save Set/ Message-ID: <00A48629.171AE8A5.3@tachysoft.com>   % >From: "AEF" <spamsink2001@yahoo.com>  >X-Newsgroups: comp.os.vms/ >Subject: Re: Help Needed: Tape Backup Save Set ! >Date: 16 Aug 2005 15:58:01 -0700    >Wayne Sewell wrote:( >> >From: "AEF" <spamsink2001@yahoo.com> >> >X-Newsgroups: comp.os.vms 2 >> >Subject: Re: Help Needed: Tape Backup Save Set$ >> >Date: 10 Aug 2005 19:52:55 -0700* >> >Organization: http://groups.google.com
 >> >Lines: 27  >> >> > >> >Z wrote: >> >> William Webb wrote:  >> >> > If you, >> >> > MOUNT/FOREIGN tape_device tape_label >> >> > You can ! >> >> > BACKUP/LIST tape_device:*  >> >> D >> >> If you're going to use BACKUP, let VMS mount the tape for you. >> >K >> >Uh, on a v5.4-1 system I had trouble using BACKUP to mount a tape. If I J >> >put in a tape that was not the first save set volume it would screw upB >> >with funny characters reported as the label. Using an explicitH >> >MOUNT/FOR made everything work fine. Ever since then I tend to do anC >> >explicit MOUNT first, except with standalone backup, of course!  >> > >> >>P >> This appears to be historical residue from the previous millenium.  I was not, >> able to reproduce this behavior on 7.3-2. >>G >> In the following example, tape DLT038 is a continuation of a saveset  >  >[example omitted] >  >> [...] >  >>Q >> Sure it got a warning message about not being at the beginning of the saveset, K >> but it certainly had no problems finding the label or mounting the tape.  >  > D >Another reason I like to MOUNT before I BACKUP is that I often haveE >very annoying and time-consuming problems with tape drives. Doing an E >explicit MOUNT helps me determine just where the problem is. Waiting G >for the load light to stop blinking before I issue any commands at all F >also helps me determine what is causing a problem. If I just pop in aG >blank tape and do a BACKUP ... /REWIND and there is trouble it is more  >difficult to troubleshoot.   N I never, *ever* have problems with tape drives, at not least since I went fromJ DAT to DLT, so I just simply have backup mount the tape every time.  Never fails.     > G >Additionally, anything that *might* cause trouble, like skipping MOUNT D >when reading the 2nd tape volume, I prefer to avoid just in case it >causes a problem. > H >Additionally**2, as lazy as I sometimes can be, it never bothered me toD >have to do a MOUNT/FOR before running BACKUP. Eventually, I did getF >into the habit of skipping the explicit MOUNT, only to have to wander- >yet again through tape-drive headache space.  > C >Remember: I am the author of "I Lost It with the Tape Drive v1.0".   H As far as habit is concerned, I rarely issue the backup command directlyN anyway.  Except for occasional quick tests to experiment with backup behavior,D all my backups, test and production, are performed by tapesys, whichL automatically constructs the command lines on the fly from backup definitionI files.  In particular, tapesys has total control of /[no]rewind, since it M always knows when new tapes are to be started.  tapesys will not even let you / try to specify the rewind qualifier yourself.     O tapesys does a manual mount, but this is for the purpose of validating that the N operator mounted the correct tape.  If not, tapesys dismounts/unloads the tapeO and tells him/her to mount the right one.  All this is done at dcl level before * even bringing vms backup into the picture.O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html    O =============================================================================== P Jake Blues:"You traded the Caddy for a microphone? ...... Okay, I can buy that."   ------------------------------    Date: 16 Aug 2005 19:56:10 -0700$ From: "AEF" <spamsink2001@yahoo.com>. Subject: Re: Help Needed: Tape Backup Save SetB Message-ID: <1124247370.345539.86310@g47g2000cwa.googlegroups.com>   Wayne Sewell wrote: ' > >From: "AEF" <spamsink2001@yahoo.com>  > >X-Newsgroups: comp.os.vms1 > >Subject: Re: Help Needed: Tape Backup Save Set # > >Date: 16 Aug 2005 15:58:01 -0700  >  > >Wayne Sewell wrote:* > >> >From: "AEF" <spamsink2001@yahoo.com> > >> >X-Newsgroups: comp.os.vms 4 > >> >Subject: Re: Help Needed: Tape Backup Save Set& > >> >Date: 10 Aug 2005 19:52:55 -0700, > >> >Organization: http://groups.google.com > >> >Lines: 27  > >> > >> > > >> >Z wrote: > >> >> William Webb wrote:  > >> >> > If you. > >> >> > MOUNT/FOREIGN tape_device tape_label > >> >> > You can # > >> >> > BACKUP/LIST tape_device:*  > >> >> F > >> >> If you're going to use BACKUP, let VMS mount the tape for you. > >> >M > >> >Uh, on a v5.4-1 system I had trouble using BACKUP to mount a tape. If I L > >> >put in a tape that was not the first save set volume it would screw upD > >> >with funny characters reported as the label. Using an explicitJ > >> >MOUNT/FOR made everything work fine. Ever since then I tend to do anE > >> >explicit MOUNT first, except with standalone backup, of course!  > >>R > >> This appears to be historical residue from the previous millenium.  I was not. > >> able to reproduce this behavior on 7.3-2. > >>I > >> In the following example, tape DLT038 is a continuation of a saveset  > >  > >[example omitted] > > 
 > >> [...] > >>S > >> Sure it got a warning message about not being at the beginning of the saveset, M > >> but it certainly had no problems finding the label or mounting the tape.  > >  > > F > >Another reason I like to MOUNT before I BACKUP is that I often haveG > >very annoying and time-consuming problems with tape drives. Doing an G > >explicit MOUNT helps me determine just where the problem is. Waiting I > >for the load light to stop blinking before I issue any commands at all H > >also helps me determine what is causing a problem. If I just pop in aI > >blank tape and do a BACKUP ... /REWIND and there is trouble it is more  > >difficult to troubleshoot.  > P > I never, *ever* have problems with tape drives, at not least since I went fromL > DAT to DLT, so I just simply have backup mount the tape every time.  Never > fails.  G Once I get a good set of TLZ drives, the jobs all tend to run fine. The D problem is later when I try to restore something and it's not on theA very same drive it was made with. Often the restore will crap out D somewhere in the middle of the tape with parity errors. A given tapeD may crap out at different places in different drives. I've had to doF restores of tapes, many of which were made before I came on the scene,G and I quite often get the stupid parity-error crap out routine. If it's G a case of alignment being different on different drives, WHY doesn't it 0 just crap out right at the beginning every time?  B Other problems I have are amusing: One drive hurled the tape out a@ couple of feet onto the floor! A "new" drive I recently got from? support often spits the tape right back out after I push it in. E Sometimes a tape gets stuck. Sometimes it protudes only 1 mm from the B front plate and cannot be pulled out nor can it be pushed back in.G Sometimes a tape comes out but snarled. One drive I got made a rattling D noise when I picked it up. A little screw fell out of it. This was aD drive I had just received to replace a broken one. Sometimes a MOUNTF operation takes over a minute and may or may not succeed. The tape mayC work perfectly well on another drive. One recent job inited a tape, B mounted it, then BACKUP compalined that the label was incorrect. AE manual mount on the same drive showed a blank label. On another drive  the label was fine.   D I am investigating switching to backups over the network, perhaps byD using NetBackup if they have something that will work on my MicroVAX3 3100 Model 95's and 80's running VMS v6.1 and v6.2.   ' I have horror stories at previous jobs.   I > >Additionally, anything that *might* cause trouble, like skipping MOUNT F > >when reading the 2nd tape volume, I prefer to avoid just in case it > >causes a problem. > > J > >Additionally**2, as lazy as I sometimes can be, it never bothered me toF > >have to do a MOUNT/FOR before running BACKUP. Eventually, I did getH > >into the habit of skipping the explicit MOUNT, only to have to wander/ > >yet again through tape-drive headache space.  > > E > >Remember: I am the author of "I Lost It with the Tape Drive v1.0".  > J > As far as habit is concerned, I rarely issue the backup command directlyP > anyway.  Except for occasional quick tests to experiment with backup behavior,F > all my backups, test and production, are performed by tapesys, whichN > automatically constructs the command lines on the fly from backup definitionK > files.  In particular, tapesys has total control of /[no]rewind, since it O > always knows when new tapes are to be started.  tapesys will not even let you / > try to specify the rewind qualifier yourself.   G Most of my backups are also done in batch. In such jobs I also prefer a F separate, explicit MOUNT command so I can better see just exactly whatD was happening when it went bonkers. And I only have to type it once!   [...]   C What is it with these tape drives? Have others had similar problems  with 4mm DAT TLZxx drives?  E I think you can now see why I err on the side of extreme caution, and ; why I wrote "I Lost It with the Tape Drive v1.0" (posted on C comp.os.vms). Check it out. It will give you better insight into my 5 frame of mind whenever I lose it with the tape drive.    ------------------------------  % Date: Wed, 17 Aug 2005 00:03:50 -0400 - From: William Webb <william.w.webb@gmail.com> . Subject: Re: Help Needed: Tape Backup Save Set7 Message-ID: <8660a3a105081621031af1c0e8@mail.gmail.com>   B On 16 Aug 2005 19:56:10 -0700, AEF <spamsink2001@yahoo.com> wrote: >=20 > Wayne Sewell wrote: ) > > >From: "AEF" <spamsink2001@yahoo.com>  > > >X-Newsgroups: comp.os.vms3 > > >Subject: Re: Help Needed: Tape Backup Save Set % > > >Date: 16 Aug 2005 15:58:01 -0700  > >  > > >Wayne Sewell wrote:, > > >> >From: "AEF" <spamsink2001@yahoo.com>! > > >> >X-Newsgroups: comp.os.vms 6 > > >> >Subject: Re: Help Needed: Tape Backup Save Set( > > >> >Date: 10 Aug 2005 19:52:55 -0700. > > >> >Organization: http://groups.google.com > > >> >Lines: 27  > > >> > > >> > > > >> >Z wrote: > > >> >> William Webb wrote:  > > >> >> > If you0 > > >> >> > MOUNT/FOREIGN tape_device tape_label > > >> >> > You can % > > >> >> > BACKUP/LIST tape_device:* 	 > > >> >> H > > >> >> If you're going to use BACKUP, let VMS mount the tape for you. > > >> >L > > >> >Uh, on a v5.4-1 system I had trouble using BACKUP to mount a tape. = If IL > > >> >put in a tape that was not the first save set volume it would screw=  up F > > >> >with funny characters reported as the label. Using an explicitL > > >> >MOUNT/FOR made everything work fine. Ever since then I tend to do a= n G > > >> >explicit MOUNT first, except with standalone backup, of course!  > > >>L > > >> This appears to be historical residue from the previous millenium.  =	 I was not 0 > > >> able to reproduce this behavior on 7.3-2. > > >>K > > >> In the following example, tape DLT038 is a continuation of a saveset  > > >  > > >[example omitted] > > >  > > >> [...] > > >>L > > >> Sure it got a warning message about not being at the beginning of th=
 e saveset,L > > >> but it certainly had no problems finding the label or mounting the t= ape. > > >  > > > H > > >Another reason I like to MOUNT before I BACKUP is that I often haveI > > >very annoying and time-consuming problems with tape drives. Doing an I > > >explicit MOUNT helps me determine just where the problem is. Waiting K > > >for the load light to stop blinking before I issue any commands at all J > > >also helps me determine what is causing a problem. If I just pop in aK > > >blank tape and do a BACKUP ... /REWIND and there is trouble it is more  > > >difficult to troubleshoot.  > > L > > I never, *ever* have problems with tape drives, at not least since I we= nt from L > > DAT to DLT, so I just simply have backup mount the tape every time.  Ne= ver 
 > > fails. >=20I > Once I get a good set of TLZ drives, the jobs all tend to run fine. The F > problem is later when I try to restore something and it's not on theC > very same drive it was made with. Often the restore will crap out F > somewhere in the middle of the tape with parity errors. A given tapeF > may crap out at different places in different drives. I've had to doH > restores of tapes, many of which were made before I came on the scene,I > and I quite often get the stupid parity-error crap out routine. If it's I > a case of alignment being different on different drives, WHY doesn't it 2 > just crap out right at the beginning every time? >=20D > Other problems I have are amusing: One drive hurled the tape out aB > couple of feet onto the floor! A "new" drive I recently got fromA > support often spits the tape right back out after I push it in. G > Sometimes a tape gets stuck. Sometimes it protudes only 1 mm from the D > front plate and cannot be pulled out nor can it be pushed back in.I > Sometimes a tape comes out but snarled. One drive I got made a rattling F > noise when I picked it up. A little screw fell out of it. This was aF > drive I had just received to replace a broken one. Sometimes a MOUNTH > operation takes over a minute and may or may not succeed. The tape mayE > work perfectly well on another drive. One recent job inited a tape, D > mounted it, then BACKUP compalined that the label was incorrect. AG > manual mount on the same drive showed a blank label. On another drive  > the label was fine.  >=20F > I am investigating switching to backups over the network, perhaps byF > using NetBackup if they have something that will work on my MicroVAX5 > 3100 Model 95's and 80's running VMS v6.1 and v6.2.  >=20) > I have horror stories at previous jobs.  >=20K > > >Additionally, anything that *might* cause trouble, like skipping MOUNT H > > >when reading the 2nd tape volume, I prefer to avoid just in case it > > >causes a problem. > > > L > > >Additionally**2, as lazy as I sometimes can be, it never bothered me t= o H > > >have to do a MOUNT/FOR before running BACKUP. Eventually, I did getJ > > >into the habit of skipping the explicit MOUNT, only to have to wander1 > > >yet again through tape-drive headache space.  > > > G > > >Remember: I am the author of "I Lost It with the Tape Drive v1.0".  > > L > > As far as habit is concerned, I rarely issue the backup command directl= y L > > anyway.  Except for occasional quick tests to experiment with backup be= havior, H > > all my backups, test and production, are performed by tapesys, whichL > > automatically constructs the command lines on the fly from backup defin= ition L > > files.  In particular, tapesys has total control of /[no]rewind, since = itL > > always knows when new tapes are to be started.  tapesys will not even l= et you1 > > try to specify the rewind qualifier yourself.  >=20I > Most of my backups are also done in batch. In such jobs I also prefer a H > separate, explicit MOUNT command so I can better see just exactly whatF > was happening when it went bonkers. And I only have to type it once! >=20 > [...]  >=20E > What is it with these tape drives? Have others had similar problems  > with 4mm DAT TLZxx drives? >=20G > I think you can now see why I err on the side of extreme caution, and = > why I wrote "I Lost It with the Tape Drive v1.0" (posted on E > comp.os.vms). Check it out. It will give you better insight into my 7 > frame of mind whenever I lose it with the tape drive.  >=20 >=20: Look at the technical differences between DAT and DLT. =20   Not insignificant..   E Also, it once was but may not be now that 4mm tapes had a tendency to A turn your 1's and 0's into 1's and ovals when the tape stretched.    WWWebb   --=20 C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  % Date: Tue, 16 Aug 2005 15:55:59 -0400 ' From: Dave Froble <davef@tsoft-inc.com> ) Subject: Re: Investigating ACCVIO problem 0 Message-ID: <11g4guok0ngg716@corp.supernews.com>   dooleys@snowy.net.au wrote: 7 > was the program previously installed with privileges?  > is it since the reboot?  > Phil >   H Exactly.  It's an access violation, not a quota issue.  It doesn't have + the privilege to do what it's trying to do.   % Possibly it was installed with privs.   I You indicate that it's run from SYSTEM.  Have you changed the authorized  L and/or default privs for that user account?  Normally, SYSTEM has all privs.   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------    Date: 16 Aug 2005 21:26:07 -0500+ From: young_r@encompasserve.org (Rob Young) % Subject: Re: Is OVMS going Bangalore? 3 Message-ID: <WZbt9kiY6HUl@eisner.encompasserve.org>   j In article <1123701854.294362.120240@o13g2000cwo.googlegroups.com>, "Ed Wilts" <ewilts@ewilts.org> writes:N >>  it just means that they have not been given any information to support the$ >> rumours of the move to India etc. > G > Perhaps there is no information to support the rumors.  It's not like H > the Inquirer is always right - remember they "pre-announced" the deathF > of the new EVA line and said that there were going to be no more newE > models?  And here HP sits, shipping 3 new models with active/active I > controllers, higher capacity, and faster IO.  Let me give you the quote  > from this story: > E > "All followups to EVA, the EVA-XL and EVA-YL are dead and gone. All E > upgrades to the current EVAs like higher capacity and faster IO are D > dead also. If you have and EVA, I hope you like it the way it is." > + > http://www.theinquirer.net/?article=18991  > H > And then there's the followup to the article above with HP denying it: > G > "I won't comment on it, take it as you will, but HP has not contacted I > me yet, ever for that matter, to tell me it is wrong. That said, I will G > stand by my story until I hear credible evidence that it is wrong. So > > far, I have only gotten re-affirmations that it is correct." > + > http://www.theinquirer.net/?article=19043  > E > Even when they're dead wrong they won't admit it.  Let's follow the G > thread a little further in the article entitled "HP attempts to shoot  > the INQUIRER messenger": > D > "HP HAS BEEN GETTING very pissy behind the scenes about my EVA andB > other related stuff."  http://www.theinquirer.net/?article=19126 > D > A month later, another article saying that the EVA line has ended:I > "The nub is HP was canning their internal storage arrays, the EVA line. & > If you ask HP, it will deny it all".+ > http://www.theinquirer.net/?article=20242  > H > So how many articles "announcing" the end of the EVA line?  Search forG > "EVA" on their site.  You'll find all the articles announcing the end 1 > of the line and ZERO announcing the new models.   ) 	And their agenda would be?  (See below).    > G > There's a reason it's called a rumor.  Refer to Webster's definition: F > " 2. A current story passing from one person to another, without any  > known authority for its truth" >     	And the most recent Inqieooops:  ) http://www.theinquirer.net/?article=23750   O "It seems that the Hitachi Itanium chipset is on it's last legs, if this were a M medical TV show, they would have already turned up the voltage on the paddles  twice.  N Betting deep throat-like sources would not put money on it seeing the light of3 day, but who knows, stranger things have happened."    	However...   F http://www.health-itworld.com/newsitems/2005/07-05/07-13-05-news-intel  N "The company will announce two new Itanium 2 processors on Monday with HitachiL Ltd., which demonstrated a chipset that supported a 667MHz front-side bus at+ the Spring Intel Developer Forum in March."     ? 	It's called agenda driven reporting.  It's interesting and fun A 	to continually point these things out.  After a while, you build D 	a portfolio of outrageous bluster that is little more than attemptsF 	to FUD things up.  Think about how many times the Inq writes articlesA 	that run IBM into the ground.  Not often at all, right?  Doesn't  	fit their agenda.  A 	You're in Minnesota... this is a bit of a departure but supports 2 	or highlights the agenda driven world we live in:   http://www.powerlineblog.com/	   The vindication of Mark Yost  O Last month St. Paul Pioneer Press associate editorial page editor Mark Yost set G off a firestorm when he wrote a "belated July 4 column" criticizing the N performance of his journalistic colleagues on matters related to the war: "WhyE they hate us." Read Yost's column -- it runs against the grain of the N predominant motifs in the media coverage of the war, but it makes a few pointsD that are borne out in abundance virtually every day on the Internet.  M Yost's column was too much for his thin-skinned colleagues. They reacted like G the wicked witch of the west to a little water thrown her way. See, for N example, a couple of the items collected here at Poynter Forums (scroll down).M Among the Poynter items is this high-minded email from Pioneer Press reporter E Chuck Laszewski to Yost: "I am embarrassed to call you my colleague." J Occasional Pioneer Press columnist Craig Westover commented here with some@ useful background on Laszewski. NRO's Media Blog took note here.  O Now comes Yost's Pioneer Press colleague and senior news editor John Welsh with K his own internal, not-for-publication contribution to the controversy in an 5 email to his news staff on "covering the home front":   O     I'm following up on a conversation during this morning's editors meeting. I L feel we could be doing a better job covering the Iraq War on the home front.L Like most newspapers, we do a good job of covering the extremes, such as theJ deaths of Minnesotans in this war. But we often fall short in covering theF daily stress and drama that the war produces in our community. I don'tM necessarily think we need to have a reporter assigned to this but I think the K paper and our readers would benefit if all of us looked for interesting war  angles on our beats.      = 	The Pioneer Press is actually embarassed by one of their own ; 	into admitting their bias and the reporters are encouraged A 	to "look for interesting war angles."   Yeah, like the fact that / 	there are good things happening there.  Hello!    	And from powerline:  N St. Paul Pioneer Press associate editorial page editor Mark Yost chastised hisO Fourth Estate colleagues in a column last month for presenting a skewed picture L of events in Iraq: "Why they hate us." The reaction to Yost's column exposedM the epidemic of thin skin among those who love to dish it out; he was more or   less invited to leave the trade.  M Yesterday Mary Katharine Ham told the story at Townhall in a terrific column: O "Knight-Ridder: Closer to the fight than the Marines." Reader Mark Pittard also O directs us to yesterday's New York Times story by Katharine Q. Seelye: "Editors J ponder how to present a broad picture of Iraq." Add these two items to theL internal Pioneer Press memo that we posted here and you might begin to think# that Mark Yost is owed an apology.     	---  C 	Point is... the Inq may never be held accountable like the Pioneer ? 	Press is by Powerline.  But who knows, maybe a blog springs up > 	that adds the power of a Slashdot without the noise that does? 	just that... points out the nonsense that some of these online ? 	trade rags and other reputable rags get away with when writing 4 	about IT subjects.  It's all about the blogs man.    D 	It took all of 24 hours and hundreds of true online experts to rip - 	apart Dan Rather's National Guard forgeries.   = 	It then took CBS 10 days to admit they couldn't authenticate 4 	the forgeries they foisted on us.  HA.  No kidding.   	New day folks!    				Rob    ------------------------------    Date: 16 Aug 2005 13:26:48 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) @ Subject: Re: Killing a process that has allocated the tape drive3 Message-ID: <W0IlV8rCngvQ@eisner.encompasserve.org>   G In article <430205c5$1@news1.ethz.ch>, S <soterroatyahoodotcom> writes:  > Larry Kilgallen wrote:F >> I think the problem is that you are just repeating, not responding. > J > Repeating is the key for understanding (roughly translated from latin), E > though it takes an open(ed) mind to grab the "brand new" idea of a   > programmable bus arbiter.  > Now please sit down.   You are still not responding.    I shall give up on you.    ------------------------------  # Date: Tue, 16 Aug 2005 18:17:06 GMT , From: "warren sander" <warren.sander@hp.com>2 Subject: Re: OpenVMS Integrity V8.2-1 New Features3 Message-ID: <C4qMe.10450$7I1.5670@news.cpqcorp.net>    fixed ) <norm.raphael@metso.com> wrote in message K news:OFC57F2177.1384A66C-ON8525705F.004B9363-8525705F.004BD8CD@metso.com...  >  > D > "Main, Kerry" <Kerry.Main@hp.com> wrote on 08/16/2005 08:25:46 AM: >   > > > -----Original Message----- > > > From: Main, Kerry # > > > Sent: August 11, 2005 6:15 PM  > > > To: Info-VAX@Mvb.Saic.Com 8 > > > Subject: RE: OpenVMS Integrity V8.2-1 New Features > > >  > > > " > > > > -----Original Message-----D > > > > From: norm.raphael@metso.com [mailto:norm.raphael@metso.com]% > > > > Sent: August 11, 2005 2:38 PM ! > > > > To: Info-VAX@Mvb.Saic.Com : > > > > Subject: Re: OpenVMS Integrity V8.2-1 New Features > > > >  > > > >  > > > > J > > > > "Main, Kerry" <Kerry.Main@hp.com> wrote on 08/11/2005 02:19:39 PM: > > > >  > > > > > All,	 > > > > > B > > > > > The list might be interested in new VMS V8.2-1 Integrity > > > release new  > > > > > features: H > > > > > http://h71000.www7.hp.com/openvms/features_benefits_chart.html > > > > # > > > > Is this available as a PDF?  > > > >  > > > L > > > The V8.2-1 doc's (including new features) should be available shortly./ > > > I'll see if I can get an update on those.  > > > 
 > > > Regards  > > >  > > 
 > > Norm - > > K > > Check out the updated VMS Integrity V8.2-1 site link - it now has a PDF  > > download option:B > > http://h71000.www7.hp.com/openvms/features_benefits_chart.html > > ! > > Thx for the feedback on this.  >  > Kerry, >  > You're welcome 8-) . >  > By the by, the PDF is marked:  > Updated: August 12, 2005 >  > The webpage is marked: > Updated: June 27, 2005 > 9 > The table on the webpage is not separately timestamped.  > ! > Are the two versions identical?  >  > -Norm  >  > >  > > :-)  > > J > > The V8.2-1 Integrity doc's should be available in the next week or so. > >  > >  > > Regards  > >  > > Kerry Main > > Senior Consultant  > > HP Services Canada > > Voice: 613-592-4660  > > Fax: 613-591-4477  > > kerryDOTmainAThpDOTcom > > (remove the DOT's and AT)  > > 8 > > OpenVMS - the secure, multi-site OS that just works. >    ------------------------------  % Date: Tue, 16 Aug 2005 14:42:59 -0400  From: norm.raphael@metso.com2 Subject: Re: OpenVMS Integrity V8.2-1 New FeaturesQ Message-ID: <OFAC7264EA.57264016-ON8525705F.0066A8F8-8525705F.0066D020@metso.com>    Updated: Auguest 12, 2005     G "warren sander" <warren.sander@hp.com> wrote on 08/16/2005 02:17:06 PM:    > fixed    Well, almost fixed:    Updated: Auguest 12, 2005    8-(     + > <norm.raphael@metso.com> wrote in message  > K news:OFC57F2177.1384A66C-ON8525705F.004B9363-8525705F.004BD8CD@metso.com...  > >  > > F > > "Main, Kerry" <Kerry.Main@hp.com> wrote on 08/16/2005 08:25:46 AM: > > " > > > > -----Original Message----- > > > > From: Main, Kerry % > > > > Sent: August 11, 2005 6:15 PM ! > > > > To: Info-VAX@Mvb.Saic.Com : > > > > Subject: RE: OpenVMS Integrity V8.2-1 New Features > > > >  > > > > $ > > > > > -----Original Message-----F > > > > > From: norm.raphael@metso.com [mailto:norm.raphael@metso.com]' > > > > > Sent: August 11, 2005 2:38 PM # > > > > > To: Info-VAX@Mvb.Saic.Com < > > > > > Subject: Re: OpenVMS Integrity V8.2-1 New Features	 > > > > > 	 > > > > > 	 > > > > > H > > > > > "Main, Kerry" <Kerry.Main@hp.com> wrote on 08/11/2005 02:19:39 PM: 	 > > > > >  > > > > > > All, > > > > > > D > > > > > > The list might be interested in new VMS V8.2-1 Integrity > > > > release new  > > > > > > features: J > > > > > > http://h71000.www7.hp.com/openvms/features_benefits_chart.html	 > > > > > % > > > > > Is this available as a PDF? 	 > > > > >  > > > > E > > > > The V8.2-1 doc's (including new features) should be available  shortly.1 > > > > I'll see if I can get an update on those.  > > > >  > > > > Regards  > > > >  > > >  > > > Norm - > > > I > > > Check out the updated VMS Integrity V8.2-1 site link - it now has a  PDF  > > > download option:D > > > http://h71000.www7.hp.com/openvms/features_benefits_chart.html > > > # > > > Thx for the feedback on this.  > > 
 > > Kerry, > >  > > You're welcome 8-) . > > ! > > By the by, the PDF is marked:  > > Updated: August 12, 2005 > >  > > The webpage is marked: > > Updated: June 27, 2005 > > ; > > The table on the webpage is not separately timestamped.  > > # > > Are the two versions identical?  > > 	 > > -Norm  > >  > > > 	 > > > :-)  > > > H > > > The V8.2-1 Integrity doc's should be available in the next week or so.  > > >  > > > 
 > > > Regards  > > >  > > > Kerry Main > > > Senior Consultant  > > > HP Services Canada > > > Voice: 613-592-4660  > > > Fax: 613-591-4477  > > > kerryDOTmainAThpDOTcom > > > (remove the DOT's and AT)  > > > : > > > OpenVMS - the secure, multi-site OS that just works. > >  >  >    ------------------------------  # Date: Tue, 16 Aug 2005 19:27:27 GMT , From: "warren sander" <warren.sander@hp.com>2 Subject: Re: OpenVMS Integrity V8.2-1 New Features3 Message-ID: <z6rMe.10458$UG1.8378@news.cpqcorp.net>   ' I never said I could speel. fixed again     ) <norm.raphael@metso.com> wrote in message K news:OFAC7264EA.57264016-ON8525705F.0066A8F8-8525705F.0066D020@metso.com...  >  > Updated: Auguest 12, 2005  >  > I > "warren sander" <warren.sander@hp.com> wrote on 08/16/2005 02:17:06 PM:  > 	 > > fixed  >  > Well, almost fixed:  >  > Updated: Auguest 12, 2005  >  > 8-(  >    ------------------------------    Date: 16 Aug 2005 13:45:25 -0700! From: kenneth.randell@verizon.net # Subject: Oracle HTTP Server anyone? B Message-ID: <1124225125.544680.94810@f14g2000cwb.googlegroups.com>  ) VMS 7.3-1, Oracle 8i (8.1.7.0.0) or 10gR1   G Does anyone have the Oracle HTTP server supplied with Oracle 8i for VMS G actually running?  If so, would you share what you did to make it work?   C It looks like all of the images are created/installed properly; the D HTTP Server (apparently based on Apache 1.3.12) starts up, but usingE the same urls/etc. as Oracle 8i installed on Windows (i.e., using the G /pls); the requests don't seem to be passed (or processed -- one of) by   the modplsql.so file image file.  G As an alternative, anyone have Oracle HTTP Server on VMS running on 10g ? yet?  I don't have a platform handy yet for testing that, as it $ requires 7.3-2 and numerous patches.   Thanks.    ------------------------------  # Date: Wed, 17 Aug 2005 00:14:25 GMT + From: Jack Patteeuw <jjpatteeuw@nospam.net> 9 Subject: Re: Print Queue in "starting" state  --  cause?? A Message-ID: <BjvMe.7877$Je.1003@newsread2.news.atl.earthlink.net>   # dave.baxter@bannerhealth.com wrote: H >      Although I have seen this every now and then, I have never really< > understood the cause.     I have a print queue (TELNETSYM)E > directed to <NODE>::<p_server>:9100 which has just been created and % > which is having a problem starting.  > > >      Looking at the queue from a different node, it shows as
 > "starting".  > I You did not say if you were using DCPS (or the version) and I don't know  2 what TELNETSYM is or where it came from  BUT  ....  G I had the same problem with the "current" version of DCPS when I tried  G to use "multiple threads" per symbiont (controlled by a logical in the  A DCPS start up)  I changed this to 1 (i.e. one queue per symbiont  # process) and the problem went away.    ------------------------------  % Date: Tue, 16 Aug 2005 13:53:07 -0400 - From: William Webb <william.w.webb@gmail.com> ) Subject: Re: Replacement for VT terminals 7 Message-ID: <8660a3a105081610532b4a900f@mail.gmail.com>   7 On 16 Aug 2005 10:37:55 -0700, tomarsin2015@comcast.net ! <tomarsin2015@comcast.net> wrote:  > Hello H > I am trying to replace all the VTs connected to the console port on my< > VAXes. I was thinking of buying a cheap pc and then addingE > some more serial ports and using Powerterm/Hyperterm. I recall that G > a long time ago someone connected the console port to a DECsever. Any  > thoughts/input would be nice. 	 > phillip  >=20 >=20  K Why would you go for greater complexity and less-than-perfect VT emulation?   B If the age of the devices is bothering you, Boundless Technologies6 took over the VT line from whichever owner dropped it.  L Or there's always Island Computer for less expensive spares with a guarante= e.   WWWebb   --=20 C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  + Date: Tue, 16 Aug 2005 19:22:59 +0000 (UTC) . From: Dale Dellutri <ddelQQQlutr@panQQQix.com>) Subject: Re: Replacement for VT terminals , Message-ID: <ddteej$ckl$1@reader2.panix.com>  > On 16 Aug 2005 10:37:55 -0700, tomarsin2015@comcast.net wrote:H > I am trying to replace all the VTs connected to the console port on my< > VAXes. I was thinking of buying a cheap pc and then addingE > some more serial ports and using Powerterm/Hyperterm. I recall that G > a long time ago someone connected the console port to a DECsever. Any  > thoughts/input would be nice.   > I did this with a Cyclades TS1000 (a 16-port console server). ? However, I assume that any terminal server that allows "reverse D telnet" would also work.  In fact, a DECserver which allows reverse . LAT connected to a VMS system would also work.  B My Cyclades is connected to a Linux machine which runs conserver. F Conserver is software which allows multiple connections to the ports, 
 logging, etc.    --  7 Dale Dellutri <ddelQQQlutr@panQQQix.com> (lose the Q's)    ------------------------------  % Date: Tue, 16 Aug 2005 16:05:06 -0400 ' From: Dave Froble <davef@tsoft-inc.com> ) Subject: Re: Replacement for VT terminals 0 Message-ID: <11g4hg56jefri5d@corp.supernews.com>   William Webb wrote: 9 > On 16 Aug 2005 10:37:55 -0700, tomarsin2015@comcast.net # > <tomarsin2015@comcast.net> wrote:  >  >>Hello H >>I am trying to replace all the VTs connected to the console port on my< >>VAXes. I was thinking of buying a cheap pc and then addingE >>some more serial ports and using Powerterm/Hyperterm. I recall that G >>a long time ago someone connected the console port to a DECsever. Any  >>thoughts/input would be nice. 	 >>phillip  >> >> >  > M > Why would you go for greater complexity and less-than-perfect VT emulation?  > D > If the age of the devices is bothering you, Boundless Technologies8 > took over the VT line from whichever owner dropped it. > O > Or there's always Island Computer for less expensive spares with a guarantee.  >  > WWWebb >   E If you usually have physical access, and with console terminals this  G seems reasonable, you can get switch boxes to connect multiple systems  6 to one terminal.  Might need to do some custom cables.  C I prefer using a 'real' VT terminal for a console.  Less potential   communication problems.   G Note that VAXstation 4000 systems don't like for the console device to  5 be disconnected, which a switch would do.  They halt.    --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Tue, 16 Aug 2005 16:05:54 -0400 2 From: "Stanley F. Quayle" <squayle@insight.rr.com>) Subject: Re: Replacement for VT terminals . Message-ID: <43020EE2.19961.F023A19@localhost>  # > <tomarsin2015@comcast.net> wrote: 	 > > Hello G > > I am trying to replace all the VTs connected to the console port on F > > my VAXes. I was thinking of buying a cheap pc and then adding someD > > more serial ports and using Powerterm/Hyperterm. I recall that aG > > long time ago someone connected the console port to a DECsever. Any ) > > thoughts/input would be nice. phillip   D I use SecureCRT (www.vandyke.com) with great success.  There's also C Reflection from WRQ.  Most terminal emulators were not designed to  < support VMS, and so don't do NumLock->PF1 or Backspace->DEL  translation.  D I have all my VMS machines connected to a terminal emulator.  Handy E for getting to the console.  Just make sure you don't have Break set  6 to Remote -- unless you want someone to halt your VAX.    + [You might want to check out CHARON-VAX at  B http://www.stanq.com/charon-vax.html     Shameless Plug(tm) alert]  
 --Stan Quayle  Quayle Consulting Inc.  
 ----------- Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363 3 8572 North Spring Ct., Pickerington, OH  43147  USA 0 stan-at-stanq-dot-com       http://www.stanq.com) "OpenVMS, when downtime is not an option"    ------------------------------    Date: 16 Aug 2005 15:55:20 -0700$ From: "AEF" <spamsink2001@yahoo.com>) Subject: Re: Replacement for VT terminals C Message-ID: <1124232920.193518.221100@o13g2000cwo.googlegroups.com>    tomarsin2015@comcast.net wrote:  > Hello H > I am trying to replace all the VTs connected to the console port on my< > VAXes. I was thinking of buying a cheap pc and then addingE > some more serial ports and using Powerterm/Hyperterm. I recall that G > a long time ago someone connected the console port to a DECsever. Any  > thoughts/input would be nice. 	 > phillip     F I use SmarTerm at work (v9.0, v10.0). It's pretty good, except I don't like its FTP interface at all.  D F1 is annoyingly not quite the same as ^S. ^S makes clean starts andG stops. F1 doesn't. It holds things up only at the terminal! So I always  disable its F1 key.   % Other than that it works pretty well.    ------------------------------  % Date: Tue, 16 Aug 2005 20:19:38 -0400 - From: William Webb <william.w.webb@gmail.com> ) Subject: Re: Replacement for VT terminals 7 Message-ID: <8660a3a105081617197006c9ca@mail.gmail.com>   4 On 8/16/05, Dave Froble <davef@tsoft-inc.com> wrote: > William Webb wrote: ; > > On 16 Aug 2005 10:37:55 -0700, tomarsin2015@comcast.net % > > <tomarsin2015@comcast.net> wrote:  > > 	 > >>Hello J > >>I am trying to replace all the VTs connected to the console port on my> > >>VAXes. I was thinking of buying a cheap pc and then addingG > >>some more serial ports and using Powerterm/Hyperterm. I recall that I > >>a long time ago someone connected the console port to a DECsever. Any ! > >>thoughts/input would be nice.  > >>phillip  > >> > >> > >  > > L > > Why would you go for greater complexity and less-than-perfect VT emulat= ion? > > F > > If the age of the devices is bothering you, Boundless Technologies: > > took over the VT line from whichever owner dropped it. > > L > > Or there's always Island Computer for less expensive spares with a guar= antee. > > 
 > > WWWebb > >  >=20F > If you usually have physical access, and with console terminals thisH > seems reasonable, you can get switch boxes to connect multiple systems8 > to one terminal.  Might need to do some custom cables. >=20D > I prefer using a 'real' VT terminal for a console.  Less potential > communication problems.  >=20H > Note that VAXstation 4000 systems don't like for the console device to7 > be disconnected, which a switch would do.  They halt.  >=20 > --6 > David Froble                       Tel: 724-529-04506 > Dave Froble Enterprises, Inc.      Fax: 724-529-0596@ > DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com > 170 Grimplin Road  > Vanderbilt, PA  15486  >=20  L Well, to 'fess up, only one of our systems at work has a VT hanging off of = it. D Each data center uses a workstation with graphics console and we useF CA-Unicenter TNG on 'em  to reach out and touch all the other machines via serial consoles.   WWWebb   --=20 C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  % Date: Tue, 16 Aug 2005 20:52:08 -0500 ( From: Wayne Sewell <wayne@tachysoft.com>) Subject: Re: Replacement for VT terminals 0 Message-ID: <00A4862C.D492BE9B.17@tachysoft.com>  . >From: William Webb <william.w.webb@gmail.com> >X-Newsgroups: comp.os.vms* >Subject: Re: Replacement for VT terminals& >Date: Tue, 16 Aug 2005 20:19:38 -0400  5 >On 8/16/05, Dave Froble <davef@tsoft-inc.com> wrote:  >> William Webb wrote:< >> > On 16 Aug 2005 10:37:55 -0700, tomarsin2015@comcast.net& >> > <tomarsin2015@comcast.net> wrote: >> >
 >> >>HelloK >> >>I am trying to replace all the VTs connected to the console port on my ? >> >>VAXes. I was thinking of buying a cheap pc and then adding H >> >>some more serial ports and using Powerterm/Hyperterm. I recall thatJ >> >>a long time ago someone connected the console port to a DECsever. Any" >> >>thoughts/input would be nice. >> >>phillip >> >>  >> >>  >> > >> >M >> > Why would you go for greater complexity and less-than-perfect VT emulat=  >ion?  >> >G >> > If the age of the devices is bothering you, Boundless Technologies ; >> > took over the VT line from whichever owner dropped it.  >> >M >> > Or there's always Island Computer for less expensive spares with a guar=  >antee.  >> > >> > WWWebb  >> > >>=20 G >> If you usually have physical access, and with console terminals this I >> seems reasonable, you can get switch boxes to connect multiple systems 9 >> to one terminal.  Might need to do some custom cables.  >>=20 E >> I prefer using a 'real' VT terminal for a console.  Less potential  >> communication problems. >>=20 I >> Note that VAXstation 4000 systems don't like for the console device to 8 >> be disconnected, which a switch would do.  They halt. >>=20  >> -- 7 >> David Froble                       Tel: 724-529-0450 7 >> Dave Froble Enterprises, Inc.      Fax: 724-529-0596 A >> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com  >> 170 Grimplin Road >> Vanderbilt, PA  15486 >>=20  > M >Well, to 'fess up, only one of our systems at work has a VT hanging off of =  >it.E >Each data center uses a workstation with graphics console and we use G >CA-Unicenter TNG on 'em  to reach out and touch all the other machines  >via serial consoles.  >   M My setup is kinda like that, except that I don't have serial lines running to M everything.  They feed into decservers.  So everything is done with the LAN.  F Which is nice because some machines are upstairs, some are downstairs.  N I have two physical vt340s, connected to the consoles of my two primary nodes,J one of which is the display node.   Once the cluster is formed, I turn offK the vt340s and all sessions consist of decterms on a vrc21 connected to the H display node.  After booting the two main nodes and establishing quorum,N everything is controlled from the one monitor.  All nodes route their decterms6 to the display node, color coded to indicate the node.  M As far as consoles, all console lines are connected to decserver 700 terminal N servers, so I can connect to any console other than the main two with LAT fromN any node in the cluster (with set host/dte).  After the two main nodes are up,N I connect to the console of each of the other nodes using LAT and boot them.    L I can also reboot any of the nodes this way as well.  I often reboot my testL nodes to a different version of vms.  I just pick one of my decterm windows,N connect to the particular console with "set host/dte", reboot the node using aG different system disk, and disconnect.  There's no need for any kind of " permanent connection to a console.  J So I never have to do any manual switching, never have to leave the VRC21,) unless I am rebooting the entire cluster. O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html    O =============================================================================== P Jake Blues:"You traded the Caddy for a microphone? ...... Okay, I can buy that."   ------------------------------  % Date: Tue, 16 Aug 2005 21:53:45 -0400 ' From: "Main, Kerry" <Kerry.Main@hp.com> ) Subject: RE: Replacement for VT terminals R Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB6B1EC2@tayexc19.americas.cpqcorp.net>   > -----Original Message-----9 > From: William Webb [mailto:william.w.webb@gmail.com]=20  > Sent: August 16, 2005 8:20 PM  > To: Info-VAX@Mvb.Saic.Com + > Subject: Re: Replacement for VT terminals  >=206 > On 8/16/05, Dave Froble <davef@tsoft-inc.com> wrote: > > William Webb wrote: = > > > On 16 Aug 2005 10:37:55 -0700, tomarsin2015@comcast.net ' > > > <tomarsin2015@comcast.net> wrote:  > > >  > > >>Hello < > > >>I am trying to replace all the VTs connected to the=20 > console port on my@ > > >>VAXes. I was thinking of buying a cheap pc and then adding@ > > >>some more serial ports and using Powerterm/Hyperterm. I=20
 > recall that @ > > >>a long time ago someone connected the console port to a=20 > DECsever. Any # > > >>thoughts/input would be nice. 
 > > >>phillip  > > >> > > >> > > >  > > > 4 > > > Why would you go for greater complexity and=20! > less-than-perfect VT emulation?  > > > H > > > If the age of the devices is bothering you, Boundless Technologies< > > > took over the VT line from whichever owner dropped it. > > > = > > > Or there's always Island Computer for less expensive=20  > spares with a guarantee. > > >  > > > WWWebb > > >  > >=20H > > If you usually have physical access, and with console terminals this< > > seems reasonable, you can get switch boxes to connect=20 > multiple systems: > > to one terminal.  Might need to do some custom cables. > >=20F > > I prefer using a 'real' VT terminal for a console.  Less potential > > communication problems.  > >=20; > > Note that VAXstation 4000 systems don't like for the=20  > console device to 9 > > be disconnected, which a switch would do.  They halt.  > >=20 > > --8 > > David Froble                       Tel: 724-529-04508 > > Dave Froble Enterprises, Inc.      Fax: 724-529-0596B > > DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com > > 170 Grimplin Road  > > Vanderbilt, PA  15486  > >=20 >=20@ > Well, to 'fess up, only one of our systems at work has a VT=20 > hanging off of it.F > Each data center uses a workstation with graphics console and we useH > CA-Unicenter TNG on 'em  to reach out and touch all the other machines > via serial consoles. >=20 > WWWebb >=20  H And as a fyi, the CA-Unicenter product was released earlier this year on" OpenVMS Integrity servers as well.  
 Reference:6 http://www3.ca.com/Press/PressRelease.aspx?CID=3D66036F "ISLANDIA, N.Y., January 17, 2005 - Computer Associates International,E Inc. (NYSE: CA) today announced that Unicenter Console Management for D OpenVMS I64 r3 is now available on HP Integrity servers based on theE Intel Itanium 2 processor. Additional Unicenter products - along with H CA's Ingres open source database - will become available on HP Integrity servers later this year."    [snip..]  G Also, another commercial product for console management (also available " on Integrity btw) is ConsoleWorks:( http://www.tditx.com/monitoringfeat.html   Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------  % Date: Tue, 16 Aug 2005 22:04:24 -0400 - From: William Webb <william.w.webb@gmail.com> ) Subject: Re: Replacement for VT terminals 7 Message-ID: <8660a3a105081619042a6ff618@mail.gmail.com>   5 On 8/16/05, Wayne Sewell <wayne@tachysoft.com> wrote: 0 > >From: William Webb <william.w.webb@gmail.com> > >X-Newsgroups: comp.os.vms, > >Subject: Re: Replacement for VT terminals( > >Date: Tue, 16 Aug 2005 20:19:38 -0400 >=207 > >On 8/16/05, Dave Froble <davef@tsoft-inc.com> wrote:  > >> William Webb wrote:> > >> > On 16 Aug 2005 10:37:55 -0700, tomarsin2015@comcast.net( > >> > <tomarsin2015@comcast.net> wrote: > >> > > >> >>HelloL > >> >>I am trying to replace all the VTs connected to the console port on = myA > >> >>VAXes. I was thinking of buying a cheap pc and then adding J > >> >>some more serial ports and using Powerterm/Hyperterm. I recall thatL > >> >>a long time ago someone connected the console port to a DECsever. An= y $ > >> >>thoughts/input would be nice. > >> >>phillip > >> >>  > >> >>  > >> > > >> >L > >> > Why would you go for greater complexity and less-than-perfect VT emu= lat=3D > >ion?  > >> >I > >> > If the age of the devices is bothering you, Boundless Technologies = > >> > took over the VT line from whichever owner dropped it.  > >> >L > >> > Or there's always Island Computer for less expensive spares with a g= uar=3D	 > >antee.  > >> >
 > >> > WWWebb  > >> >	 > >>=3D20 I > >> If you usually have physical access, and with console terminals this K > >> seems reasonable, you can get switch boxes to connect multiple systems ; > >> to one terminal.  Might need to do some custom cables. 	 > >>=3D20 G > >> I prefer using a 'real' VT terminal for a console.  Less potential  > >> communication problems.	 > >>=3D20 K > >> Note that VAXstation 4000 systems don't like for the console device to : > >> be disconnected, which a switch would do.  They halt.	 > >>=3D20  > >> -- 9 > >> David Froble                       Tel: 724-529-0450 9 > >> Dave Froble Enterprises, Inc.      Fax: 724-529-0596 C > >> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com  > >> 170 Grimplin Road > >> Vanderbilt, PA  15486	 > >>=3D20  > > L > >Well, to 'fess up, only one of our systems at work has a VT hanging off = of =3D > >it.G > >Each data center uses a workstation with graphics console and we use I > >CA-Unicenter TNG on 'em  to reach out and touch all the other machines  > >via serial consoles.  > >  >=20L > My setup is kinda like that, except that I don't have serial lines runnin= g to, > everything.  They feed into decservers.=20  8 Well, duh, if you have more than two systems to monitor!  . I figured that the DECservers were understood.  ( I promise to be more explicit next time.   WWWebb  # So everything is done with the LAN. H > Which is nice because some machines are upstairs, some are downstairs. >=20L > I have two physical vt340s, connected to the consoles of my two primary n= odes, L > one of which is the display node.   Once the cluster is formed, I turn of= f L > the vt340s and all sessions consist of decterms on a vrc21 connected to t= heJ > display node.  After booting the two main nodes and establishing quorum,L > everything is controlled from the one monitor.  All nodes route their dec= terms 8 > to the display node, color coded to indicate the node. >=20L > As far as consoles, all console lines are connected to decserver 700 term= inalL > servers, so I can connect to any console other than the main two with LAT=  from L > any node in the cluster (with set host/dte).  After the two main nodes ar= e up, L > I connect to the console of each of the other nodes using LAT and boot th= em.  >=20L > I can also reboot any of the nodes this way as well.  I often reboot my t= est L > nodes to a different version of vms.  I just pick one of my decterm windo= ws, L > connect to the particular console with "set host/dte", reboot the node us= ing a I > different system disk, and disconnect.  There's no need for any kind of $ > permanent connection to a console. >=20L > So I never have to do any manual switching, never have to leave the VRC21= , + > unless I am rebooting the entire cluster. K > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= L =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=L =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D L > Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysof= t.com : > http://www.tachysoft.com/www/tachyon.html and wayne.htmlK > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= L =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=L =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D L > Jake Blues:"You traded the Caddy for a microphone? ...... Okay, I can buy=  that."  >=20     --=20 C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  % Date: Tue, 16 Aug 2005 21:56:39 -0500 ( From: Wayne Sewell <wayne@tachysoft.com>) Subject: Re: Replacement for VT terminals 0 Message-ID: <00A48635.D81DE825.11@tachysoft.com>  . >From: William Webb <william.w.webb@gmail.com> >X-Newsgroups: comp.os.vms* >Subject: Re: Replacement for VT terminals8 >Message-ID: <8660a3a105081619042a6ff618@mail.gmail.com>& >Date: Tue, 16 Aug 2005 22:04:24 -0400  6 >On 8/16/05, Wayne Sewell <wayne@tachysoft.com> wrote:1 >> >From: William Webb <william.w.webb@gmail.com>  >> >X-Newsgroups: comp.os.vms - >> >Subject: Re: Replacement for VT terminals ) >> >Date: Tue, 16 Aug 2005 20:19:38 -0400  >>=20 8 >> >On 8/16/05, Dave Froble <davef@tsoft-inc.com> wrote: >> >> William Webb wrote: ? >> >> > On 16 Aug 2005 10:37:55 -0700, tomarsin2015@comcast.net ) >> >> > <tomarsin2015@comcast.net> wrote:  >> >> > 
 >> >> >>Hello M >> >> >>I am trying to replace all the VTs connected to the console port on =  >my B >> >> >>VAXes. I was thinking of buying a cheap pc and then addingK >> >> >>some more serial ports and using Powerterm/Hyperterm. I recall that M >> >> >>a long time ago someone connected the console port to a DECsever. An=  >y% >> >> >>thoughts/input would be nice.  >> >> >>phillip  >> >> >> >> >> >> >> >> >  >> >> > M >> >> > Why would you go for greater complexity and less-than-perfect VT emu=  >lat=3D  >> >ion? >> >> > J >> >> > If the age of the devices is bothering you, Boundless Technologies> >> >> > took over the VT line from whichever owner dropped it. >> >> > M >> >> > Or there's always Island Computer for less expensive spares with a g=  >uar=3D 
 >> >antee. >> >> >  >> >> > WWWebb >> >> > 
 >> >>=3D20J >> >> If you usually have physical access, and with console terminals thisL >> >> seems reasonable, you can get switch boxes to connect multiple systems< >> >> to one terminal.  Might need to do some custom cables.
 >> >>=3D20H >> >> I prefer using a 'real' VT terminal for a console.  Less potential >> >> communication problems. 
 >> >>=3D20L >> >> Note that VAXstation 4000 systems don't like for the console device to; >> >> be disconnected, which a switch would do.  They halt. 
 >> >>=3D20 >> >> --: >> >> David Froble                       Tel: 724-529-0450: >> >> Dave Froble Enterprises, Inc.      Fax: 724-529-0596D >> >> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com >> >> 170 Grimplin Road  >> >> Vanderbilt, PA  15486 
 >> >>=3D20 >> >M >> >Well, to 'fess up, only one of our systems at work has a VT hanging off =  >of =3D  >> >it. H >> >Each data center uses a workstation with graphics console and we useJ >> >CA-Unicenter TNG on 'em  to reach out and touch all the other machines >> >via serial consoles. >> > >>=20 M >> My setup is kinda like that, except that I don't have serial lines runnin=  >g to - >> everything.  They feed into decservers.=20  > 9 >Well, duh, if you have more than two systems to monitor!  > / >I figured that the DECservers were understood.  > ) >I promise to be more explicit next time.  >     K Sorry, I'm not familiar with these console consolidators.  Thought it might F have some sort of hardware component that brought in the serial lines.  L The only console consolidator I ever looked at was the original one from theM mid-to-late eighties.  Don't remember what it was called, but it *did* have a I discrete serial line to every console, a hardware/software combo.  Did it L deliberately, using fiber optics.  IIRC, electrical isolation was the reason for doing it that way.O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html    O =============================================================================== P Jake Blues:"You traded the Caddy for a microphone? ...... Okay, I can buy that."   ------------------------------  # Date: Wed, 17 Aug 2005 03:50:52 GMT + From: Ken Robinson <sendspamhere@rbnsn.com> ) Subject: Re: Replacement for VT terminals B Message-ID: <1124250652.49ef9bb30f2b611455041d648ed8e820@teranews>  + Wayne Sewell <wayne@tachysoft.com> wrote in 3 news:00A48635.D81DE825.11@tachysoft.com (in part):    0 >>I figured that the DECservers were understood. >>* >>I promise to be more explicit next time. >> >  > G > Sorry, I'm not familiar with these console consolidators.  Thought it G > might have some sort of hardware component that brought in the serial 	 > lines.   > E > The only console consolidator I ever looked at was the original one H > from the mid-to-late eighties.  Don't remember what it was called, but: > it *did* have a discrete serial line to every console, aE > hardware/software combo.  Did it deliberately, using fiber optics.  B > IIRC, electrical isolation was the reason for doing it that way.  F If you're talking about the original one from DEC, it was called VCS. F When I was at Bellcore in the mid '80s we went to see on of the first H prototypes. It was running on a VAX 780. When we implemented it, we ran D it on an MicroVAX II running the windowing system before DECwindows.  G VCS turned into PCM (Polycenter Console Manager) which got sold to CA.  F Another company (TDI <http://www.tditx.com/>) came out with a console G manager called ConsoleWorks. I used it when I was at Verizon Wireless.  G The consoles all go into a DECserver and it gets the OPA0: output from  H each console. You can use either a web based interface (it has it's own H webserver) or a command line interface to access the different consoles.  I I liked to use any of the console managers, since they allow you (if you  G have the permissions) to do anything you could do from a local console.    Ken Robinson kenrbnsn (at) rbnsn (dot) com    ------------------------------    Date: 16 Aug 2005 21:07:26 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: SAMBA for VMS, Message-ID: <4302558e$1@news.langstoeger.at>  ` In article <430149A0.64F1775E@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> writes:! >Peter 'EPLAN' LANGSTOEGER wrote: f >> In article <S$w4BegPtECc@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:Q >> >> Look for VMS freeware LD V8 to get the .ZIP file with the .HLB and the .CLD  >> >K >> >So even given the freeware, it is not sufficient to install the command ( >> >file, you also need to install ZIP ? >>  , >> No, my fault. LD V8 is already a PCSI kit > C >I believe there should also be a .PCSI$COMPRESSED kit (transfer as ) >binary, no need to SET FILE/ATTRIBUTES).   2 No. .PCSI$COMPRESSED does also need a SET FILE/ATT. A .DCXEXE did not and a .ZIPEXE does also not.I So, ZIPSFX (with .PCSI or .PCSI$COMPRESSED contained) is the way to go...    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Tue, 16 Aug 2005 15:49:49 -0400 ' From: Dave Froble <davef@tsoft-inc.com>  Subject: Re: SAMBA for VMS0 Message-ID: <11g4gja2bdvvh2f@corp.supernews.com>   Bill Gunshannon wrote:- > In article <4301494D.76D8EFC2@comcast.net>, 7 > 	David J Dachtera <djesys.nospam@comcast.net> writes:  >  >>Larry Kilgallen wrote: >>	 >>>[snip] H >>>People should understand that not everybody is allow to use Freeware. >>H >>So you're telling me that there is a business opportunity out there toG >>sell "sensitive sites" the same things they can get at no cost to the & >>taxpayer through the usual channels? >  > F > There's a lot ore to it than just selling soething that is availableG > for free.  Not being allowed to use Freeware tends to mean only fully H > supported software is allowed.  If you want to sell Freeware with fullF > support then you have found your niche market, but most people mightJ > shy away from that.  People here are always asking if others are willingE > to bet their business on the likes of Linux.  For some, the same is  > true about all Freeware!!   H It's about trust.  Do you trust the software?  Do you trust the vendor? ?   Supported or not doesn't mean much if you don't trust either.   G If a company offered a statement that they had vetted the copy of some  G freeware, and insure that it has no hidden security problems and such,  I and further state that they will provide support, fixes, and such, for a  E fee, then what's the difference between that and any other purchased   software?  Including VMS.   2 Do you trust their capability to vet the software?  9 Do you trust them to be responsive if you have a problem?   : Do you trust them to have the ability to fix any problems?  C Are they financially large enough to sue if they do not perform as   contracted?   @ Sad thing is, if seems to always come down to the last question.   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------    Date: 16 Aug 2005 15:29:03 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen)  Subject: Re: SAMBA for VMS3 Message-ID: <qKkv40i6Tnlb@eisner.encompasserve.org>   Z In article <11g4gja2bdvvh2f@corp.supernews.com>, Dave Froble <davef@tsoft-inc.com> writes:  I > If a company offered a statement that they had vetted the copy of some  I > freeware, and insure that it has no hidden security problems and such,  K > and further state that they will provide support, fixes, and such, for a  G > fee, then what's the difference between that and any other purchased   > software?  Including VMS.   F If a company makes such a statement, the cautious customer will ensureG an executed support agreement is in place before they use the software.   B Then there is no difference from the contractual approach for VMS.  E > Are they financially large enough to sue if they do not perform as  
 > contracted?  > B > Sad thing is, if seems to always come down to the last question.  A That is the same as for VMS, like the people who would not use it ! because it did not come from IBM.    ------------------------------    Date: 16 Aug 2005 16:40:30 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)  Subject: Re: SAMBA for VMS3 Message-ID: <o5hvWt0IiFZ7@eisner.encompasserve.org>   W In article <3m6ch4F15k2ckU1@individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes:  > B > I have  no software capable of burning a CD that even has a clueB > what a .ods file is.  And that certainly seems like an awful lot. > of extra work to just install one package.    F    Try to lie to it and tell it it's an ISO image.  In both cases it'sE    a block by block copy of the CD with no idea what's really in each A    block and no particular interest in the contents of the block.    ------------------------------    Date: 16 Aug 2005 16:42:10 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)  Subject: Re: SAMBA for VMS3 Message-ID: <E3Ayy5DIaAyh@eisner.encompasserve.org>   ] In article <slrndfs4mj.gva.usenet@zappy.catbert.org>, Dan Foster <usenet@evilphb.org> writes: d > In article <VO5$2o0o8q68@eisner.encompasserve.org>, Larry Kilgallen <Kilgallen@SpamCop.net> wrote: >>< >> "LD" does not seem to be a command on my VMS V7.3 system. > D > I think LD was bundled with VMS starting with V7.3-1? I'm not sure) > LDDRIVER ever shipped with OpenVMS/VAX.  > G >> Perhaps you meant to specify that some software beyond VMS should be  >> installed first.  > D > The Freeware CD does include LDDRIVER and works great on Alpha. No% > idea if it works with VAX (or I64).   D    Yep, works on a VAX.  I was the only way I could check some ODS-1=    syntax stuff I put into some code just for the heck of it.    ------------------------------    Date: 16 Aug 2005 16:44:01 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)  Subject: Re: SAMBA for VMS3 Message-ID: <F0z3yCUb3HPl@eisner.encompasserve.org>   c In article <42FDE0E9.11775.59A6E1E@localhost>, "Stanley F. Quayle" <squayle@insight.rr.com> writes:  > D > Shame you can't wait for OpenVMS Engineering to develop their own 7 > Samba implementation.  Should be ready to go Q2 2006.   B    Your a couple decades too late.  And you've got the cart before
    the horse.   A    The original author of Samba based it on packet sniffing while     running Pathworks.    ------------------------------  % Date: Tue, 16 Aug 2005 15:41:59 -0400 ' From: Dave Froble <davef@tsoft-inc.com> 0 Subject: Re: SAMBA for VMS (The saga continues!)0 Message-ID: <11g4g4kf9v3sg5b@corp.supernews.com>   John Malmberg wrote: > Bill Gunshannon wrote: >  >>F >>> Here's details from my account on Deathrow, this has been used to E >>> build Perl which also chokes on memory with a standard account...  >>> ? >>> : Maxjobs:         0  Fillm:       300  Bytlm:       128000 ? >>> : Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0 ? >>> : Maxdetach:       0  BIOlm:       150  JTquota:       8192 ? >>> : Prclm:          10  DIOlm:       150  WSdef:         4000 ? >>> : Prio:            4  ASTlm:       250  WSquo:        10000 ? >>> : Queprio:         0  TQElm:        40  WSextent:     16384 ? >>> : CPU:        (none)  Enqlm:      2000  Pgflquo:     128000    Short discussion on quotas.   G I'd reduce the WSdef back to something reasonable on a VAX.  My memory  D is that the OS will attempt to start with this size of working set. I Many things on a VAX will not use this much memory, much less keeping it  G tied up while doing nothing.  It will also depend upon how much memory   you have to spread around.   Maybe:   WSdef = 500  WSquo = 2500 WSextent = 25000 to 50000   F Note that the process will only get into the extent if free memory is E available.  If it's not being user, and someone can use it, then let  @ them have as much as they can use.  When the free memory is not D available, processes will not be given hugh chunks over their quota.  B I had a customer who thought more was better.  Wanted to speed up I things.  Set the WSdef extremely high, higher that the quota and extent.  G   Ended up with a snail.  You need to understand what VMS will do with  5 certain things, such as WSdef, before making changes.   I Most quotas are just that.  Set them high, but only what's required will  H be used.  Some things, defaults are high on the list, tell VMS where to ) start.  These can be much more sensitive.    --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------   Date: 16 Aug 2005 19:57:34 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)0 Subject: Re: SAMBA for VMS (The saga continues!), Message-ID: <3meupdF16knluU1@individual.net>  I OK, it all compiled.  Now the next problem.  The webpage where I got this G said there might be a problem with "snprintf".  There was.  He provides E an OBJ that can be added into SAMBA.OLB.  One problem.  It's an Alpha F OBJ file.  Anybody know where I can get the source so I can compile itF and add it to the OLB by hand?  It can't be that big if someone has itH and is willing to email it to me.  With that, I suspect that I will haveA SAMBA ready to try.  Wether or not it works is the next question.    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------   Date: 16 Aug 2005 20:01:42 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)0 Subject: Re: SAMBA for VMS (The saga continues!), Message-ID: <3mev16F16knluU2@individual.net>  , In article <3meupdF16knluU1@individual.net>,+ 	bill@cs.uofs.edu (Bill Gunshannon) writes:  > K > OK, it all compiled.  Now the next problem.  The webpage where I got this I > said there might be a problem with "snprintf".  There was.  He provides G > an OBJ that can be added into SAMBA.OLB.  One problem.  It's an Alpha H > OBJ file.  Anybody know where I can get the source so I can compile itH > and add it to the OLB by hand?  It can't be that big if someone has itJ > and is willing to email it to me.  With that, I suspect that I will haveC > SAMBA ready to try.  Wether or not it works is the next question.  >   F Never mind.  I searched thru the sources and snprintf.c is there.  NowF I don't understand why it is not just included in the first place, but at least I can move on.    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------    Date: 16 Aug 2005 13:35:21 -0700 From: phil@rephil.org # Subject: simh define/attach printer C Message-ID: <1124224521.155599.131050@z14g2000cwz.googlegroups.com>    Hi,   E I'm trying to set up simh to output text on a file, when printing.  I G have looked, but am unable to find the info in a form I can comprehend. F  Pardon the newbie-ish questions.  Also pardon the lengthy msg; I haveD included what I hope is the necessary output from the system if someF kind soul can help me straighten my head out.  (I'm sure the system is! doing just what I tell it to!) ;)    Some pertinent info:    SIMH 3.4 VAX under Linux *    VMS 7.2 (working well enough otherwise)  F Q:  Under simh 3.4, is it necessary to 'attach lpt <output_file>' when) configuring the emulator?  (Did, no joy.)   A I am new at configuring queues, so this may be my problem, but on  startup I get:   --------A The OpenVMS VAX system is now executing the site-specific startup 	 commands.   8 %%%%%%%%%%%  OPCOM  16-AUG-2005 13:46:59.85  %%%%%%%%%%%( Message from user QUEUE_MANAGE on ERSATZA %QMAN-I-QUENOTSTART, queue SYS$PRINT could not be started on node  ERSATZ  8 %%%%%%%%%%%  OPCOM  16-AUG-2005 13:46:59.90  %%%%%%%%%%%( Message from user QUEUE_MANAGE on ERSATZ- -SYSTEM-W-NOSUCHDEV, no such device available   - %SYSTEM-W-NOSUCHDEV, no such device available  %JBC-E-NOSUCHQUE, no such queue F %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 8   SYSTEM       job terminated at 16-AUG-2005 13:47:02.72 -----     E I ran START/QUEUE/MANAGER/NEW initially, so that seems to be alright. % The lines from SYSTARTUP_VMS.COM are:      ------------------------------- ? $ DEFINE /SYSTEM $PRINTER  _LPA0:     ! if using a line printer . $ SET PRINTER /NOWRAP /NOTRUNCATE /CR $PRINTER: $ SET DEVICE /SPOOLED=(SYS$PRINT, SYS$SYSDEVICE:) $PRINTER $ ENABLE AUTOSTART /QUEUES $ START /QUEUE SYS$PRINT -------------------------------      If I try from a shell:     -------------------------------  $ start/queue sys$print - %SYSTEM-W-NOSUCHDEV, no such device available  $ # -----------------------------------      What does the device look like?      ---------------------- $ show dev/full lpa0:   C Printer LPA0:, device type RA92, is online, record-oriented device,  carriage>     control, device is spooled through an intermediate device.  <     Error count                    0    Operations completed       2 1     Owner process                 ""    Owner UIC  [SYSTEM]0     Owner process ID        00000000    Dev Prot S:RWPL,O:RWPL,G,W ;     Reference count                0    Default buffer size       80 3     Page width                    80    Page Length       66 1     Carriage_return     Formfeed        Uppercase 3     No Passall          Wrap            No Printall 3     No Fallback         No Tab          No Truncate      Intermediate device: DUA0:"     Associated queue:    SYS$PRINT   $      ------------------------  C BIG QUESTION:  Why the hell does the printer look like an RA92 disk G drive?  Should it?  What device type should the printer be assigned for  the simulated LPT in simh?   TIA, Phil Mendelsohn    ------------------------------  % Date: Tue, 16 Aug 2005 19:02:33 -0400 ' From: Dave Froble <davef@tsoft-inc.com> ' Subject: Re: simh define/attach printer 0 Message-ID: <11g4rsntc5fnrcf@corp.supernews.com>   phil@rephil.org wrote: > Hi,  > G > I'm trying to set up simh to output text on a file, when printing.  I I > have looked, but am unable to find the info in a form I can comprehend. H >  Pardon the newbie-ish questions.  Also pardon the lengthy msg; I haveF > included what I hope is the necessary output from the system if someH > kind soul can help me straighten my head out.  (I'm sure the system is# > doing just what I tell it to!) ;)  >  > Some pertinent info: >    SIMH 3.4 VAX under Linux , >    VMS 7.2 (working well enough otherwise) > H > Q:  Under simh 3.4, is it necessary to 'attach lpt <output_file>' when+ > configuring the emulator?  (Did, no joy.)  > C > I am new at configuring queues, so this may be my problem, but on  > startup I get: > 
 > --------C > The OpenVMS VAX system is now executing the site-specific startup  > commands.  > : > %%%%%%%%%%%  OPCOM  16-AUG-2005 13:46:59.85  %%%%%%%%%%%* > Message from user QUEUE_MANAGE on ERSATZC > %QMAN-I-QUENOTSTART, queue SYS$PRINT could not be started on node  > ERSATZ > : > %%%%%%%%%%%  OPCOM  16-AUG-2005 13:46:59.90  %%%%%%%%%%%* > Message from user QUEUE_MANAGE on ERSATZ/ > -SYSTEM-W-NOSUCHDEV, no such device available  > / > %SYSTEM-W-NOSUCHDEV, no such device available ! > %JBC-E-NOSUCHQUE, no such queue H > %SET-I-INTSET, login interactive limit = 64, current interactive value > = 0 : >   SYSTEM       job terminated at 16-AUG-2005 13:47:02.72 > -----  >  > G > I ran START/QUEUE/MANAGER/NEW initially, so that seems to be alright. ' > The lines from SYSTARTUP_VMS.COM are:  >  > ! > ------------------------------- A > $ DEFINE /SYSTEM $PRINTER  _LPA0:     ! if using a line printer 0 > $ SET PRINTER /NOWRAP /NOTRUNCATE /CR $PRINTER< > $ SET DEVICE /SPOOLED=(SYS$PRINT, SYS$SYSDEVICE:) $PRINTER  I Ok, here's where things start.  To set a device /SPOOLED means that when  C that device is opened for output, data is not sent directly to the  I device, but to a temporary file on some disk, and when the device (file)  : is closed, then it is sent to the actual device (printer).  ? I find it good to omit the spooling until I get things working  I correctly.  With simh, which I've never used, I'd really want to be sure  B that there was an operational device before I used the SET DEVICE  /SPOOLED option.  H I'm wondering whether simh has a device called LPA0.  That's your first  thing to check.    > $ ENABLE AUTOSTART /QUEUES > $ START /QUEUE SYS$PRINT! > -------------------------------  >  >  > If I try from a shell: >  > ! > -------------------------------  > $ start/queue sys$print / > %SYSTEM-W-NOSUCHDEV, no such device available  > $ % > -----------------------------------  >  > ! > What does the device look like?  >  >  > ---------------------- > $ show dev/full lpa0:  > E > Printer LPA0:, device type RA92, is online, record-oriented device, 
 > carriage@ >     control, device is spooled through an intermediate device. > > >     Error count                    0    Operations completed	 >       2 3 >     Owner process                 ""    Owner UIC 
 > [SYSTEM]2 >     Owner process ID        00000000    Dev Prot > S:RWPL,O:RWPL,G,W = >     Reference count                0    Default buffer size 	 >      80 5 >     Page width                    80    Page Length 	 >      66 3 >     Carriage_return     Formfeed        Uppercase 5 >     No Passall          Wrap            No Printall 5 >     No Fallback         No Tab          No Truncate   >     Intermediate device: DUA0:$ >     Associated queue:    SYS$PRINT >  > $  >  >  > ------------------------ > E > BIG QUESTION:  Why the hell does the printer look like an RA92 disk  > drive?  Should it?  I You've set the device to have all output directed to it to be spooled to  ! temporary files on the RA92 disk.   6 >  What device type should the printer be assigned for > the simulated LPT in simh? >  > TIA, > Phil Mendelsohn  >      --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------    Date: 16 Aug 2005 17:08:17 -0700* From: "Alan Greig" <greigaln@netscape.net>' Subject: Re: simh define/attach printer C Message-ID: <1124237297.178644.277750@z14g2000cwz.googlegroups.com>    Dave Froble wrote:     > I > I'm wondering whether simh has a device called LPA0.  That's your first  > thing to check.   = It does. Another thing I've just noticed is that he will need  $ SET PRINTER LPA0/NOUPPER  D Or else everything is in uppercase. My we are emulating old hardware :-)   G I'm guessing he's just got some broken device name setup for the queue.  --  
 Alan greig   ------------------------------    Date: 16 Aug 2005 18:24:14 -0700 From: phil@rephil.org ' Subject: Re: simh define/attach printer C Message-ID: <1124241854.853463.251890@z14g2000cwz.googlegroups.com>   F Thanks gents -- I'm making a bit of progress.  I notice, however, thatD with the printer *NOT* spooled, nothing gets written to my text fileD until SIMH halts -- i.e., if I issue SHUTDOWN to VMS, it's not untilA the console returns to the 'sim> ' prompt that the output file is  written to.    Am I missing something?    Cheers,  Phil Mendelsohn    ------------------------------  # Date: Tue, 16 Aug 2005 21:19:44 GMT L From: winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing) Subject: Re: Squid for VMS6 Message-ID: <00A485F6.0381F6B6@SSRL.SLAC.STANFORD.EDU>   In article <Pine.GSO.4.10.10508161140040.657-100000@solaris.polarhome.com>, Volker Englisch <eh41@solaris.polarhome.com> writes: >Hi, > K >I'm wondering if there is something like squid for OpenVMS? There seems to K >be no port of squid to this OS. Is there maybe another http-proxy software 
 >for OpenVMS?    SWS/Apache has proxy services.  O I couldn't find a squid port for VMS when I went looking a couple of years ago.   L (But if you're planning to do organization-wide proxy cache with hundreds orN thousands of users, I'd get a cheap fast x86 box with lots of RAM and lots of L fast cheap disk, either netboot it (proxably with netBSD) or boot it off CD,N and just run squid on it.  Except for your configuration files, you don't careO whether you lose any of the data on the system - you're always  rebuilding your  proxy cache anyway.)   -- Alan    ------------------------------   Date: 17 Aug 2005 01:09:39 GMT( From: bill@cs.uofs.edu (Bill Gunshannon), Subject: Re: The Educational License Program, Message-ID: <3mfh2jF16uk96U1@individual.net>  , In article <eVEttEv6DQX4@malvm3.mala.bc.ca>,4 	nothome@spammers.are.scum (Malcolm Dunnett) writes:/ > In article <3mc45jF16c3d9U1@individual.net>,  / >    bill@cs.uofs.edu (Bill Gunshannon) writes:  >> Sue, D >>   Now that you seem to have taken over the EDU Program I hope you& >> don't mind if I ask you a question. >>  E >>   The EDU Licenses all expire on 31 Aug.  Will the new licenses be C >> available before the old ones expire?  That is about 8 days into B >> the new semester and a real bad time to have the students loose >> access to the machine.  >>   > B >   Well I'm not Sue ( or Johnny Cash for that matter ) but I can C > tell you the new licenses have been available since the beginning @ > of August or so. You need to re-register your school and get a/ > new ID in order to download the new licenses.  >   B That doesn't make any sense. Why would you have to re-register and= get a new number?  If the number is a throw away, why bother?    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------    Date: 16 Aug 2005 19:46:30 -07001 From: nothome@spammers.are.scum (Malcolm Dunnett) , Subject: Re: The Educational License Program, Message-ID: <6vFnLqsJmbj2@malvm9.mala.bc.ca>  - In article <3mfh2jF16uk96U1@individual.net>,  -    bill@cs.uofs.edu (Bill Gunshannon) writes:    >>  C >>   Well I'm not Sue ( or Johnny Cash for that matter ) but I can  D >> tell you the new licenses have been available since the beginningA >> of August or so. You need to re-register your school and get a 0 >> new ID in order to download the new licenses. >>   > D > That doesn't make any sense. Why would you have to re-register and? > get a new number?  If the number is a throw away, why bother?  >   $    Go ahead, shoot the messenger :-)  H    It's my experience that I need to re-register each year, after Aug 1,F in order to get new licenses that are valid for that year. Perhaps I'mH not supposed to have to, but I did so and was able to get licenses valid/ until Aug 31,2006. I suggest you give it a try.    ------------------------------    Date: 16 Aug 2005 11:27:16 -0700" From: dave.baxter@bannerhealth.com< Subject: Was -->  Print Queue in "starting" state -- cause??C Message-ID: <1124216836.148437.108330@g14g2000cwa.googlegroups.com>   G    I want to try and clarify the problem a little.    This is not about E system startup, is is about problems starting an exist print queue as  shown below;     $ show queue/full isab3 Printer queue ISAB, stopped, autostart inactive, on ) XXXXX1::"ISAB:9100", mounted form DEFAULT G   <LEXMARK 4039, BH CORP, 1F, TECH SERVICES on server ISAB, port 9100 >   K /AUTOSTART_ON=(XXXXX1::"ISAB:9100",XXXXX2::"ISAB:9100",XXXXX3::"ISAB:9100") ?   /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) /LIBRARY=SYSSETUPLEX 0   /OWNER=[SYS,SYSTEM] /PROCESSOR=TCPIP$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S)    /SCHEDULE=(NOSIZE) $  $ enable autostart /queues $  $ show queue/full isab3 Printer queue ISAB, stopped, autostart inactive, on ) XXXXX1::"ISAB:9100", mounted form DEFAULT G   <LEXMARK 4039, BH CORP, 1F, TECH SERVICES on server ISAB, port 9100 >   K /AUTOSTART_ON=(XXXXX1::"ISAB:9100",XXXXX2::"ISAB:9100",XXXXX3::"ISAB:9100") ?   /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) /LIBRARY=SYSSETUPLEX 0   /OWNER=[SYS,SYSTEM] /PROCESSOR=TCPIP$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S)    /SCHEDULE=(NOSIZE) $  $   {queue did not start!!!) $  $ start/queue isab    :      :    :.    <process hung -- wait several minutes (>5)> Ctrl_Y	 Interrupt  $  $ show queue/full isabB Printer queue ISAB, starting, on XXXXX1::"ISAB:9100", mounted form DEFAULT G   <LEXMARK 4039, BH CORP, 1F, TECH SERVICES on server ISAB, port 9100 >   K /AUTOSTART_ON=(XXXXX1::"ISAB:9100",XXXXX2::"ISAB:9100",XXXXX3::"ISAB:9100") ?   /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) /LIBRARY=SYSSETUPLEX 0   /OWNER=[SYS,SYSTEM] /PROCESSOR=TCPIP$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S)    /SCHEDULE=(NOSIZE) $ G Queue will now stay in this state indefinitely, or until $ stop[/reset]   G     Fortunately this is happening in my non-production cluster.   In my C production cluster it doesn't seem to be a problem (yet).   The one G major difference I see between the two clusters is  that in the cluster B where I am NOT having any problems, the Logical QMAN$MASTER is notB defined.   However, on the node where the I am having the problem, QMAN$MASTER IS defined. B     I turned on /Autostart back at the beginning of July without aC problem. and the only event that occurred since then was a complete G shutdown of my non-prod (and prod) clusters for a power cutover on 27th  July. @     <It is interesting to note that this coincides with the lastD modification of the QMAN$MASTER.DAT, but that might be exactly that, i.e. coincidence.>  D I am currently running OVMS 7.3-2, and TCPIP 5.4, ECO 4.    I am notF aware of any outstanding patches for either of these, relating to QMAN or JOBCONTROL.  	 Any ideas    Dave.                  John Vottero wrote: A > "David J Dachtera" <djesys.nospam@comcast.net> wrote in message ' > news:43014BD2.B4DAAAC2@comcast.net...  > > John Santos wrote: > >>( > >> dave.baxter@bannerhealth.com wrote:M > >> >      Although I have seen this every now and then, I have never really A > >> > understood the cause.     I have a print queue (TELNETSYM) J > >> > directed to <NODE>::<p_server>:9100 which has just been created and* > >> > which is having a problem starting. > >> >C > >> >      Looking at the queue from a different node, it shows as  > >> > "starting". > >> >J > >> >      The queue is being created by a process on a different clusterJ > >> > using the TCPIP$REXEC process.    The process has been successfullyH > >> > used through several VMS and TCPIP upgrades for more than 3 yearsK > >> > without this problem.    Right now, the parent process is hanging up > > >> > because the queue on the remote cluster will not start. > >> >N > >> >      The only thing which has changed is that I recently enabled all ofJ > >> > the print queues on this cluster for "autostart".   However the newJ > >> > queues are not init'd "/autostart" (because I haven't got around to  > >> > modifying the script yet. > >> > > >>H > >> This is purely a guess, but since no one else has responded yet :-) > >>H > >> Are you sure the queues aren't trying to start befoe TCPIP is fully@ > >> up?  I.E. is your "$ start/queue/manager" too early in your > >> systartup_vms.com?  > >>< > >> Added info, on checking my own systems:  It appears the= > >> "$ start/queue/manager" command has disappeared from the A > >> template file, so presumably is no longer required. However, B > >> it seems to start up TCPIP ($ @SYS$STARTUP:TCPIP$STARTUP.COM)> > >> after all the queue starting stuff, so maybe autostart on' > >> network printer queues is a no-no?  > > J > > At some point, not sure when, this was added into the startup sequence > > outside of SYSTARTUP_VMS.  > > K > > I was kinda hoping someone inside HP/OVMS/TCPIP Engr. would pipe up and D > > explain how to deal with this (queue manager starting before the# > > environment is ready for that).  > K > I'm not OpenVMS Engineering but, I'll pipe up anyway.  Starting the queue N > manager doesn't start any queues.  Autostart queues don't start until you doN > an "ENABLE AUTOSTART/QUEUES".  Non autostart queues don't start until you doN > a "START/QUEUE".  Make sure that your environment is ready before you enable > autostart queues.  > K > Also, the OP mentioned updating the INITs in his script.  It's unclear if N > he's talking about his startup scripts but, there's no reason to INIT queuesJ > during startup and if you have a lot of queues you can seriously improveN > startup speed by eliminating the unnecessary INITS.  The only queue commands; > needed during startup are the ENABLE and/or START/QUEUEs.  >  >  > > E > > Then again, you couldn't do what LPD$STARTUP needs to do if queue & > > manager (at least) wasn't running. > >  > > Hhmm... A puzzlement...    ------------------------------    Date: 16 Aug 2005 11:26:51 -0700" From: dave.baxter@bannerhealth.com< Subject: Was -->  Print Queue in "starting" state -- cause??C Message-ID: <1124216811.938614.183980@g44g2000cwa.googlegroups.com>   G    I want to try and clarify the problem a little.    This is not about E system startup, is is about problems starting an exist print queue as  shown below;     $ show queue/full isab3 Printer queue ISAB, stopped, autostart inactive, on ) XXXXX1::"ISAB:9100", mounted form DEFAULT G   <LEXMARK 4039, BH CORP, 1F, TECH SERVICES on server ISAB, port 9100 >   K /AUTOSTART_ON=(XXXXX1::"ISAB:9100",XXXXX2::"ISAB:9100",XXXXX3::"ISAB:9100") ?   /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) /LIBRARY=SYSSETUPLEX 0   /OWNER=[SYS,SYSTEM] /PROCESSOR=TCPIP$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S)    /SCHEDULE=(NOSIZE) $  $ enable autostart /queues $  $ show queue/full isab3 Printer queue ISAB, stopped, autostart inactive, on ) XXXXX1::"ISAB:9100", mounted form DEFAULT G   <LEXMARK 4039, BH CORP, 1F, TECH SERVICES on server ISAB, port 9100 >   K /AUTOSTART_ON=(XXXXX1::"ISAB:9100",XXXXX2::"ISAB:9100",XXXXX3::"ISAB:9100") ?   /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) /LIBRARY=SYSSETUPLEX 0   /OWNER=[SYS,SYSTEM] /PROCESSOR=TCPIP$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S)    /SCHEDULE=(NOSIZE) $  $   {queue did not start!!!) $  $ start/queue isab    :      :    :.    <process hung -- wait several minutes (>5)> Ctrl_Y	 Interrupt  $  $ show queue/full isabB Printer queue ISAB, starting, on XXXXX1::"ISAB:9100", mounted form DEFAULT G   <LEXMARK 4039, BH CORP, 1F, TECH SERVICES on server ISAB, port 9100 >   K /AUTOSTART_ON=(XXXXX1::"ISAB:9100",XXXXX2::"ISAB:9100",XXXXX3::"ISAB:9100") ?   /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) /LIBRARY=SYSSETUPLEX 0   /OWNER=[SYS,SYSTEM] /PROCESSOR=TCPIP$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S)    /SCHEDULE=(NOSIZE) $ G Queue will now stay in this state indefinitely, or until $ stop[/reset]   G     Fortunately this is happening in my non-production cluster.   In my C production cluster it doesn't seem to be a problem (yet).   The one G major difference I see between the two clusters is  that in the cluster B where I am NOT having any problems, the Logical QMAN$MASTER is notB defined.   However, on the node where the I am having the problem, QMAN$MASTER IS defined. B     I turned on /Autostart back at the beginning of July without aC problem. and the only event that occurred since then was a complete G shutdown of my non-prod (and prod) clusters for a power cutover on 27th  July. @     <It is interesting to note that this coincides with the lastD modification of the QMAN$MASTER.DAT, but that might be exactly that, i.e. coincidence.>  D I am currently running OVMS 7.3-2, and TCPIP 5.4, ECO 4.    I am notF aware of any outstanding patches for either of these, relating to QMAN or JOBCONTROL.  	 Any ideas    Dave.                  John Vottero wrote: A > "David J Dachtera" <djesys.nospam@comcast.net> wrote in message ' > news:43014BD2.B4DAAAC2@comcast.net...  > > John Santos wrote: > >>( > >> dave.baxter@bannerhealth.com wrote:M > >> >      Although I have seen this every now and then, I have never really A > >> > understood the cause.     I have a print queue (TELNETSYM) J > >> > directed to <NODE>::<p_server>:9100 which has just been created and* > >> > which is having a problem starting. > >> >C > >> >      Looking at the queue from a different node, it shows as  > >> > "starting". > >> >J > >> >      The queue is being created by a process on a different clusterJ > >> > using the TCPIP$REXEC process.    The process has been successfullyH > >> > used through several VMS and TCPIP upgrades for more than 3 yearsK > >> > without this problem.    Right now, the parent process is hanging up > > >> > because the queue on the remote cluster will not start. > >> >N > >> >      The only thing which has changed is that I recently enabled all ofJ > >> > the print queues on this cluster for "autostart".   However the newJ > >> > queues are not init'd "/autostart" (because I haven't got around to  > >> > modifying the script yet. > >> > > >>H > >> This is purely a guess, but since no one else has responded yet :-) > >>H > >> Are you sure the queues aren't trying to start befoe TCPIP is fully@ > >> up?  I.E. is your "$ start/queue/manager" too early in your > >> systartup_vms.com?  > >>< > >> Added info, on checking my own systems:  It appears the= > >> "$ start/queue/manager" command has disappeared from the A > >> template file, so presumably is no longer required. However, B > >> it seems to start up TCPIP ($ @SYS$STARTUP:TCPIP$STARTUP.COM)> > >> after all the queue starting stuff, so maybe autostart on' > >> network printer queues is a no-no?  > > J > > At some point, not sure when, this was added into the startup sequence > > outside of SYSTARTUP_VMS.  > > K > > I was kinda hoping someone inside HP/OVMS/TCPIP Engr. would pipe up and D > > explain how to deal with this (queue manager starting before the# > > environment is ready for that).  > K > I'm not OpenVMS Engineering but, I'll pipe up anyway.  Starting the queue N > manager doesn't start any queues.  Autostart queues don't start until you doN > an "ENABLE AUTOSTART/QUEUES".  Non autostart queues don't start until you doN > a "START/QUEUE".  Make sure that your environment is ready before you enable > autostart queues.  > K > Also, the OP mentioned updating the INITs in his script.  It's unclear if N > he's talking about his startup scripts but, there's no reason to INIT queuesJ > during startup and if you have a lot of queues you can seriously improveN > startup speed by eliminating the unnecessary INITS.  The only queue commands; > needed during startup are the ENABLE and/or START/QUEUEs.  >  >  > > E > > Then again, you couldn't do what LPD$STARTUP needs to do if queue & > > manager (at least) wasn't running. > >  > > Hhmm... A puzzlement...    ------------------------------  # Date: Tue, 16 Aug 2005 21:04:54 GMT % From: "John Vottero" <John@mvpsi.com> @ Subject: Re: Was -->  Print Queue in "starting" state -- cause??< Message-ID: <WxsMe.1390$AT7.1058@newssvr22.news.prodigy.net>  0 <dave.baxter@bannerhealth.com> wrote in message = news:1124216811.938614.183980@g44g2000cwa.googlegroups.com... H >   I want to try and clarify the problem a little.    This is not aboutG > system startup, is is about problems starting an exist print queue as  > shown below; >  >  > $ show queue/full isab5 > Printer queue ISAB, stopped, autostart inactive, on + > XXXXX1::"ISAB:9100", mounted form DEFAULT H >  <LEXMARK 4039, BH CORP, 1F, TECH SERVICES on server ISAB, port 9100 > > M > /AUTOSTART_ON=(XXXXX1::"ISAB:9100",XXXXX2::"ISAB:9100",XXXXX3::"ISAB:9100") @ >  /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) /LIBRARY=SYSSETUPLEX1 >  /OWNER=[SYS,SYSTEM] /PROCESSOR=TCPIP$TELNETSYM  > /PROTECTION=(S:M,O:D,G:R,W:S)  >  /SCHEDULE=(NOSIZE)  > $  > $ enable autostart /queues > $  > $ show queue/full isab5 > Printer queue ISAB, stopped, autostart inactive, on + > XXXXX1::"ISAB:9100", mounted form DEFAULT H >  <LEXMARK 4039, BH CORP, 1F, TECH SERVICES on server ISAB, port 9100 > > M > /AUTOSTART_ON=(XXXXX1::"ISAB:9100",XXXXX2::"ISAB:9100",XXXXX3::"ISAB:9100") @ >  /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) /LIBRARY=SYSSETUPLEX1 >  /OWNER=[SYS,SYSTEM] /PROCESSOR=TCPIP$TELNETSYM  > /PROTECTION=(S:M,O:D,G:R,W:S)  >  /SCHEDULE=(NOSIZE)  > $  > $   {queue did not start!!!)    I The queue did not start because it was in an "autostart inactive" state.  M This means that it's an autostart queue but, someone did a STOP/QUEUE on it.  D If you STOP and autostart queue, it won't autostart untill you do a  START/QUEUE on it.     > $  > $ start/queue isab >   :      :    : / >   <process hung -- wait several minutes (>5)>  > Ctrl_Y > Interrupt  > $  > $ show queue/full isabD > Printer queue ISAB, starting, on XXXXX1::"ISAB:9100", mounted form	 > DEFAULT H >  <LEXMARK 4039, BH CORP, 1F, TECH SERVICES on server ISAB, port 9100 > > M > /AUTOSTART_ON=(XXXXX1::"ISAB:9100",XXXXX2::"ISAB:9100",XXXXX3::"ISAB:9100") @ >  /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) /LIBRARY=SYSSETUPLEX1 >  /OWNER=[SYS,SYSTEM] /PROCESSOR=TCPIP$TELNETSYM  > /PROTECTION=(S:M,O:D,G:R,W:S)  >  /SCHEDULE=(NOSIZE)  > $ I > Queue will now stay in this state indefinitely, or until $ stop[/reset]      What happens when you do:    $ TELNET  ISAB  9100   ------------------------------    Date: 16 Aug 2005 14:27:47 -0700" From: dave.baxter@bannerhealth.com? Subject: Re: Was --> Print Queue in "starting" state -- cause?? C Message-ID: <1124227666.975023.100750@o13g2000cwo.googlegroups.com>   G  If you notice John, I executed an "$ enable autostart /queues" command D right after the first "show queue".    The second "show queue" is to show that nothing happened.   C again refering to my previous post, I then executed a "start/Queue"  command and the process hung.    In response to your question,    MILLC1$SYSMGR>> telnet isab ( %TELNET-I-TRYING, Trying ... nn.nn.n.1151 %TELNET-I-SESSION, Session 01, host isab, port 23 ( HP JetDirectCAPE, Escape character is ^] Password is not set   8 Please type "menu" for the MENU system, or "?" for help, or "/" for current settings.>   = what do you think.    ISAB is out there and is pingable, etc. = I'm wondering if my QUEUE DB and Journal files are corrupted.    Dave.    ------------------------------  # Date: Wed, 17 Aug 2005 00:22:31 GMT % From: "John Vottero" <John@mvpsi.com> ? Subject: Re: Was --> Print Queue in "starting" state -- cause?? < Message-ID: <brvMe.1872$Z%6.1186@newssvr17.news.prodigy.com>  0 <dave.baxter@bannerhealth.com> wrote in message = news:1124227666.975023.100750@o13g2000cwo.googlegroups.com... H > If you notice John, I executed an "$ enable autostart /queues" commandF > right after the first "show queue".    The second "show queue" is to > show that nothing happened.   G Yes, I saw that.  What I was trying to say is that the behaviour is as  M expected.  If you STOP/QUEUE an autostart queue, it's won't restart when you  M do an ENABLE AUTOSTART.  You have to do a START/QUEUE to bring it out of the   "autostart inactive" state.    > E > again refering to my previous post, I then executed a "start/Queue"  > command and the process hung.  >  > In response to your question,  >  > MILLC1$SYSMGR>> telnet isab    You missed the "9100", try:    telnet isab 9100      * > %TELNET-I-TRYING, Trying ... nn.nn.n.1153 > %TELNET-I-SESSION, Session 01, host isab, port 23 * > HP JetDirectCAPE, Escape character is ^] > Password is not set  > : > Please type "menu" for the MENU system, or "?" for help, > or "/" for current settings.>  > ? > what do you think.    ISAB is out there and is pingable, etc. ? > I'm wondering if my QUEUE DB and Journal files are corrupted.  >  > Dave.  >    ------------------------------   End of INFO-VAX 2005.457 ************************