1 INFO-VAX	Sun, 02 Oct 2005	Volume 2005 : Issue 550       Contents:D Re: Auto-disabling screen saver on Alpha VMS V7.3-2, DWMOTIF V1.3-1?D Re: Auto-disabling screen saver on Alpha VMS V7.3-2, DWMOTIF V1.3-1?B Getting Management attention for operations integrity (was ;32767)F Re: Getting Management attention for operations integrity (was ;32767)F Re: Getting Management attention for operations integrity (was ;32767)F Re: Getting Management attention for operations integrity (was ;32767)F Re: Getting Management attention for operations integrity (was ;32767)F Re: Getting Management attention for operations integrity (was ;32767) Install a Printer on VMS Q Re: Pipe & MySQL Re: Pipe & MySQL RE: Time to produce EV79s! RE: Time to produce EV79s! Re: Vamp Hacked! Re: Vamp Hacked! Re: Vamp Hacked! Re: [OT] - dealing with ;32767  F ----------------------------------------------------------------------  # Date: Sun, 02 Oct 2005 14:32:54 GMT * From: "FredK" <fred.nospam@nospam.dec.com>M Subject: Re: Auto-disabling screen saver on Alpha VMS V7.3-2, DWMOTIF V1.3-1? 3 Message-ID: <qcS%e.13627$KS5.4231@news.cpqcorp.net>   J A co-worker is sneaking in an changing it?  A program is altering it?  YouE have a home session defined (and no current session - or perhaps when D you moved the system disk you screwed up file ownership protections)H and somehow it is overriding the settings?  In any case, I've never seen this behavior.  D The "blank" screen setting by default on the Oxygen VX1 should causeD the device driver to put the screen into power-saver mode.  The onlyB way this won't happen is if something (or someone) has changed the& setting of "prefer blanking" to false.  K I would look at the contents of the resource files in [.dt...] as the first E likely suspect.  I would then look for something that is running XSET ? (from DECW$UTILS) to change the screen saver settings.  If none H of those are at fault, then I would look at the system resource files in> CDE$SYSTEM_COMMON:[*...] to see if they have been altered.  IfK not I would then suspect an application is doing it.  If not - then I would  look for ghosts in the machine.     7 "Steven M. Schweda" <sms@antinode.org> wrote in message , news:05100122124580_2020028F@antinode.org...J >    I've recently noticed that the screen saver/lock on my ("new") XP1000I > seems to be disabling itself from time to time.  I set the times in the E > Style Manager - Screen dialog in the New Desktop (30 minutes and 60 F > minutes), and enable both.  If I re-open the dialog immediately, theI > settings appear as I set them.  Then I remain logged in for some hours. H > Eventually, I notice that the screen isn't saved and/or locked when itG > should be, and if I re-open the Screen dialog I see that it's back to D > Screen Saver Off, 10 minutes (grayed), Screen Lock Off, 60 minutesD > (grayed).  Am I alone, or is this a common problem?  Any known (or > suspected) reason? > G >    The hardware is an XP1000 (500MHz) with a 3Dlabs Oxygen VX1 with a A > system disk which came from an AlpSta 200 4/233 with a PBXGA-BA E > (ZXLp-E2).  I believe that the patches are pretty close to current. 5 > PRODUCT SHOW PRODUCT /FULL mentions (among others):  > 0 > VMS V7.3-2                      DWMOTIF V1.3-16 > VMS732_GRAPHICS V4.0            DWMOTIF_ECO02 V1.3-1 > VMS732_SYS V8.0  > VMS732_UPDATE V4.0 > VMS732_VMSMUP V1.0 > I >    And speaking of "screen savers" which are actually "screen wasters", I > I know that there's no significant VMS workstation market any more, but J > is there any hope of ever seeing a true screen saver, that is, one whichI > shuts off the video signal and lets the ("ENERGY STAR") CRT really save = > itself ("sleep mode", "http://www.energystar.gov/index.cfm? I > fuseaction=find_a_product.showProductGroup&pgw_code=MO")?  And then, if   > it could just stay engaged ... > J > ------------------------------------------------------------------------ > 6 >    Steven M. Schweda               (+1) 651-699-98185 >    382 South Warwick Street        sms@antinode-org  >    Saint Paul  MN  55105-2547    ------------------------------  % Date: Sun, 02 Oct 2005 19:34:45 +0200 & From: Paul Sture <paul.sture@decus.ch>M Subject: Re: Auto-disabling screen saver on Alpha VMS V7.3-2, DWMOTIF V1.3-1? + Message-ID: <3qak1mFdt0ujU1@individual.net>    Steven M. Schweda wrote:  H  >Eventually, I notice that the screen isn't saved and/or locked when itG  >should be, and if I re-open the Screen dialog I see that it's back to D  >Screen Saver Off, 10 minutes (grayed), Screen Lock Off, 60 minutesD  >(grayed).  Am I alone, or is this a common problem?  Any known (or  >suspected) reason?  D I can't say that I've seen this behaviour, but I do know that after G changing screen saver settings, unless you log off, saving the current  E session, a system crash (or shutdown without logging out of DWMOTIF)   will lose the changes.  , > From: "FredK" <fred.nospam@nospam.dec.com> > , >>A co-worker is sneaking in an changing it? >  > : >    SYSTEM and I are the only users, and I'm SYSTEM, too. >   F Has SYSTEM logged off meanwhile, resaving the original settings? From C the date of CURRENT.DIR below (28-SEP-2005), this is a possibility.      >>  A program is altering it?  >  > G >    I don't know of any clever enough to do that, but I'll keep an eye  > open.   H If you look in your accounting log, you will see a ton of subprocesses, G by default every 3? minutes, which do the screen blanking. This period  F can be extended, but without DWMOTIF in front of me I cannot remember I how to change it. I am wondering if either this or something else within  1 DWMOTIF might be re-reading the CURRENT settings.    >  >>  You G >>have a home session defined (and no current session - or perhaps when F >>you moved the system disk you screwed up file ownership protections), >>and somehow it is overriding the settings? >  > I >    Startup says "Resume current session", but I'm not logging out, just I > walking away.  Does BACKUP /IMAGE screw up file ownership protections?  J > (I had planned simply to move the disk, but when I heard it at power-up,F > for the first time in a couple of years, I decided that a fresh disk > would be safer.) >  >   >>  In any case, I've never seen >>this behavior. >  > - >    I always like to be on the cutting edge.  > , > Directory SYS$SYSROOT:[SYSMGR.DT.SESSIONS] > K > CURRENT.DIR;1               1  28-SEP-2005 16:24:50.44  (RWED,RWED,RE,RE) K > CURRENT_FONT.DIR;1          1  30-MAY-1999 20:18:11.17  (RWED,RWED,RE,RE) K > CURRENT_OLD.DIR;1           1   2-SEP-2005 21:34:23.71  (RWED,RWED,RE,RE) I > DTWMFP.SESSION;1            1  28-SEP-2005 16:24:51.27  (RWED,RWED,RE,)  >  > Total of 4 files, 4 blocks.   I I suggest you change the settings as desired, then log out from DWMOTIF,  A saving Current as you go. Painful I know if you have a gazillion  D connections to other systems, but it's the only way I found to make 
 things stick.    ------------------------------   Date: 2 Oct 2005 09:49:52 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen) K Subject: Getting Management attention for operations integrity (was ;32767) 3 Message-ID: <is5nDvBzJ7FZ@eisner.encompasserve.org>    > Larry Kilgallen wrote: > F >> The recently release US Federal Government NIST SP 800-53 has a setI >> of rules that would avoid such malfeasance.  I hope it will be adopted & >> by the HIPPA/SOX/GLB crowd as well.  1 		Let me give a sample, based on but not quoting, 0 		a redacted posting.  Section numbers below are/ 		from 800-53 except where otherwise specified.    CA-2 SECURITY ASSESSMENTS   @ Control: The organization conducts an assessment of the security@    controls in the information system [Assignment: organization-A     defined frequency, at least annually] to determine the extent @    to which the controls are implemented correctly, operating as>    intended, and producing the desired outcome with respect to4    meeting the security requirements for the system.  > Supplemental Guidance: This control is intended to support theD    FISMA requirement that the management, operational, and technicalA    controls in each information system contained in the inventory D    of major information systems be tested with a frequency depending@    on risk, but no less than annually. NIST Special PublicationsG    800-53A and 800-26 provide guidance on security control assessments.   2 		So all the items listed below (as well as others0 		in the document) are subject to annual review./ 		Particularly, the selection criteria for CA-7 1 		Continuous Monitoring will be reviewed, and any . 		reviewer worth their salt on VMS will expect0 		inclusions of those items for which Continuous2 		Monitoring will be efficient.  Mechanical tests,6 		like last backup date, should certainly be included.   CA-7 CONTINUOUS MONITORING  ? Control: The organization monitors the security controls in the +     information system on an ongoing basis.   ? Supplemental Guidance: Continuous monitoring activities include =    configuration management and control of information system A    components, security impact analyses of changes to the system, A    ongoing assessment of security controls, and status reporting. B    The organization establishes the selection criteria for control?    monitoring and subsequently selects a subset of the security ?    controls employed within the information system for purposes     of continuous monitoring.  3 		Techies will recognize that Continuous Monitoring 2 		is not truly Continuous, as that would mean that4 		no CPU cycles could be used for any other purpose.5 		In my view a combination of weekly checks for items 4 		that require scanning all disks, and hourly checks4 		for other mechanical tests like SYSUAF privileges.   CP-9 INFORMATION SYSTEM BACKUP  < Control: The organization conducts backups of user-level and@    system-level information (including system state information)A    contained in the information system [Assignment: organization- 9    defined frequency] and stores backup information at an "    appropriately secured location.  B Supplemental Guidance: The frequency of information system backupsC    and the transfer rate of backup information to alternate storage B    sites (if so designated) are consistent with the organization's:    recovery time objectives and recovery point objectives.   Control Enhancements:   : (1) The organization tests backup information [Assignment:>    organization-defined frequency] to ensure media reliability    and information integrity.   ? (2) The organization selectively uses backup information in the E    restoration of information system functions as part of contingency     plan testing.  A (3) The organization stores backup copies of the operating system ?    and other critical information system software in a separate ?    facility or in a fire-rated container that is not collocated !    with the operational software.   2 		Control Enhancements are required for systems of+ 		higher sensitivity according to FIPS-199.   , IR-1 INCIDENT RESPONSE POLICY AND PROCEDURES  B Control: The organization develops, disseminates, and periodically?    reviews/updates: (i) a formal, documented, incident response A    policy that addresses purpose, scope, roles, responsibilities, <    and compliance; and (ii) formal, documented procedures to@    facilitate the implementation of the incident response policy-    and associated incident response controls.   B Supplemental Guidance: The incident response policy and proceduresE    are consistent with applicable federal laws, directives, policies, E    regulations, standards, and guidance. The incident response policy E    can be included as part of the general information security policy F    for the organization. Incident response procedures can be developedH    for the security program in general, and for a particular informationB    system, when required. NIST Special Publication 800-61 providesH    guidance on incident handling and reporting. NIST Special Publication@    800-12 provides guidance on security policies and procedures.  1 		Procedures for incident handling are subject to , 		the yearly review mentioned in CA-2 above.   IR-2 INCIDENT RESPONSE TRAINING   < Control: The organization trains personnel in their incident:    response roles and responsibilities with respect to theB    information system and provides refresher training [Assignment:6    organization-defined frequency, at least annually].   Supplemental Guidance: None.   Control Enhancements:   @ (1) The organization incorporates simulated events into incidentB    response training to facilitate effective response by personnel    in crisis situations.  C (2) The organization employs automated mechanisms to provide a more /    thorough and realistic training environment.   , 		Adequacy of training is subject to review.   CM-2 BASELINE CONFIGURATION   > Control: The organization develops, documents, and maintains a@    current, baseline configuration of the information system and7    an inventory of the systemas constituent components.   B Supplemental Guidance: The configuration of the information systemA    is consistent with the Federal Enterprise Architecture and the @    organizationas information system architecture. The inventory@    of information system components includes manufacturer, type,>    serial number, version number, and location (i.e., physical>    location and logical position within the information system    architecture).    Control Enhancements:   = (1) The organization updates the baseline configuration as an ?    integral part of information system component installations.   = (2) The organization employs automated mechanisms to maintain ;    an up-to-date, complete, accurate, and readily available     baseline configuration.  / 		Hardware supposed to be in use is documented.   % CM-4 MONITORING CONFIGURATION CHANGES   = Control: The organization monitors changes to the information <    system and conducts security impact analyses to determine    the effects of the changes.  B Supplemental Guidance: The organization documents the installationA    of information system components. After the information system @    is changed, the organizations checks the security features to:    ensure the features are still functioning properly. The?    organization audits activities associated with configuration %    changes to the information system.   + 		Changes to hardware in use are monitored.    IA-5 AUTHENTICATOR MANAGEMENT   C Control: The organization manages information system authenticators E    (e.g., tokens, PKI certificates, biometrics, passwords, key cards) D    by: (i) defining initial authenticator content; (ii) establishingD    administrative procedures for initial authenticator distribution,D    for lost/compromised, or damaged authenticators, and for revokingA    authenticators; and (iii) changing default authenticators upon #    information system installation.   B Supplemental Guidance: Users take reasonable measures to safeguardF    authenticators including maintaining possession of their individualE    authenticators, not loaning or sharing authenticators with others, @    and reporting lost or compromised authenticators immediately.=    For password-based authentication, the information system: :    (i) protects passwords from unauthorized disclosure and;    modification when stored and transmitted; (ii) prohibits >    passwords from being displayed when entered; (iii) enforces:    password minimum and maximum lifetime restrictions; and:    (iv) prohibits password reuse for a specified number of=    generations. For PKI-based authentication, the information 7    system: (i) validates certificates by constructing a 7    certification path to an accepted trust anchor; (ii) =    establishes user control of the corresponding private key; A    and (iii) maps the authenticated identity to the user account. >    FIPS 201 and Special Publications 800-73 and 800-76 specify<    a personal identity verification (PIV) card token for use=    in the unique identification and authentication of federal =    employees and contractors. NIST Special Publication 800-63 9    provides guidance on remote electronic authentication.    		No default passwords.   A =================================================================   > 800-53 contains requirements obvious to skilled practitioners,9 but it does constitute official rules (mandatory with the < publication of FIPS-200 this coming December) for US federal government systems.     = For other organizations, 800-53 is the finest "best practice"  description I have seen.   ------------------------------  % Date: Sun, 02 Oct 2005 17:39:36 +0200 & From: Paul Sture <paul.sture@decus.ch>O Subject: Re: Getting Management attention for operations integrity (was ;32767) + Message-ID: <3qad9pFdnj4aU1@individual.net>    Larry Kilgallen wrote:   <snip>   Thanks for that Larry. > D > Supplemental Guidance: Users take reasonable measures to safeguardH >    authenticators including maintaining possession of their individualG >    authenticators, not loaning or sharing authenticators with others, B >    and reporting lost or compromised authenticators immediately.? >    For password-based authentication, the information system: < >    (i) protects passwords from unauthorized disclosure and= >    modification when stored and transmitted; (ii) prohibits @ >    passwords from being displayed when entered; (iii) enforces< >    password minimum and maximum lifetime restrictions; and                ^^^^^^^? I have never understood the logic of minimum password lifetime  - restrictions, so am surprised to see it here.    Can anyone enlighten me please?    ------------------------------  $ Date: Sun, 2 Oct 2005 11:55:52 -0400' From: Ken Robinson <kenrbnsn@gmail.com> O Subject: Re: Getting Management attention for operations integrity (was ;32767) G Message-ID: <7dd80f60510020855vd59bfcfr27b5dee47aa38964@mail.gmail.com>   = On 10/2/05, Paul Sture <paul.sture@decus.ch> wrote (in part):  > Larry Kilgallen wrote:B > >    passwords from being displayed when entered; (iii) enforces> > >    password minimum and maximum lifetime restrictions; and >                ^^^^^^^@ > I have never understood the logic of minimum password lifetime/ > restrictions, so am surprised to see it here.  > ! > Can anyone enlighten me please?  > A  I believe that a minimum password lifetime will not let a person ? change their passwords within a certain time limit of the first  change.   F This would be useful if you're not using history lists and allow usersF to repeat passwords often. It would stop people who would change their@ passwords and then immediately change them back to the original,# thereby keeping their old password.    Ken    ------------------------------   Date: 2 Oct 2005 11:09:24 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen) O Subject: Re: Getting Management attention for operations integrity (was ;32767) 3 Message-ID: <8g1UG9TIfWJS@eisner.encompasserve.org>   q In article <7dd80f60510020855vd59bfcfr27b5dee47aa38964@mail.gmail.com>, Ken Robinson <kenrbnsn@gmail.com> writes: ? > On 10/2/05, Paul Sture <paul.sture@decus.ch> wrote (in part):  >> Larry Kilgallen wrote: C >> >    passwords from being displayed when entered; (iii) enforces ? >> >    password minimum and maximum lifetime restrictions; and  >>                ^^^^^^^ A >> I have never understood the logic of minimum password lifetime 0 >> restrictions, so am surprised to see it here. >>" >> Can anyone enlighten me please? >>C >  I believe that a minimum password lifetime will not let a person A > change their passwords within a certain time limit of the first 	 > change.  > H > This would be useful if you're not using history lists and allow usersH > to repeat passwords often. It would stop people who would change theirB > passwords and then immediately change them back to the original,% > thereby keeping their old password.   8 On certain operating systems from the Pacific Northwest,5 I believe one can change the password enough times to 9 overflow the password history space and cause the desired 2 password to fall off the end and thus be reusable.  > VMS prevents that attack cold by requiring generated passwords> at that point, but lesser operating systems don't seem to have figured it out.    ------------------------------   Date: 2 Oct 2005 11:13:02 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen) O Subject: Re: Getting Management attention for operations integrity (was ;32767) 3 Message-ID: <p80vQuecXsk0@eisner.encompasserve.org>   c In article <8g1UG9TIfWJS@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes: s > In article <7dd80f60510020855vd59bfcfr27b5dee47aa38964@mail.gmail.com>, Ken Robinson <kenrbnsn@gmail.com> writes: @ >> On 10/2/05, Paul Sture <paul.sture@decus.ch> wrote (in part): >>> Larry Kilgallen wrote:D >>> >    passwords from being displayed when entered; (iii) enforces@ >>> >    password minimum and maximum lifetime restrictions; and >>>                ^^^^^^^B >>> I have never understood the logic of minimum password lifetime1 >>> restrictions, so am surprised to see it here.  >>> # >>> Can anyone enlighten me please?  >>> D >>  I believe that a minimum password lifetime will not let a personB >> change their passwords within a certain time limit of the first
 >> change. >>  I >> This would be useful if you're not using history lists and allow users I >> to repeat passwords often. It would stop people who would change their C >> passwords and then immediately change them back to the original, & >> thereby keeping their old password. > : > On certain operating systems from the Pacific Northwest,7 > I believe one can change the password enough times to ; > overflow the password history space and cause the desired 4 > password to fall off the end and thus be reusable. > @ > VMS prevents that attack cold by requiring generated passwords@ > at that point, but lesser operating systems don't seem to have > figured it out.   @ For US Federal Government systems, one should call that superiorC VMS mechanism a "compensating control" if anyone asks about minimum D password lifetimes.  The term "compensating control" is described inC great detail in the documents, but basically it means what it says.    ------------------------------  % Date: Sun, 02 Oct 2005 19:40:55 +0200 & From: Paul Sture <paul.sture@decus.ch>O Subject: Re: Getting Management attention for operations integrity (was ;32767) + Message-ID: <3qakd7Fdb9erU1@individual.net>    Larry Kilgallen wrote:e > In article <8g1UG9TIfWJS@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:  > s >>In article <7dd80f60510020855vd59bfcfr27b5dee47aa38964@mail.gmail.com>, Ken Robinson <kenrbnsn@gmail.com> writes:  >>@ >>>On 10/2/05, Paul Sture <paul.sture@decus.ch> wrote (in part): >>>  >>>>Larry Kilgallen wrote: >>>>C >>>>>   passwords from being displayed when entered; (iii) enforces ? >>>>>   password minimum and maximum lifetime restrictions; and  >>>> >>>>               ^^^^^^^B >>>>I have never understood the logic of minimum password lifetime1 >>>>restrictions, so am surprised to see it here.  >>>># >>>>Can anyone enlighten me please?  >>>> >>> D >>> I believe that a minimum password lifetime will not let a personB >>>change their passwords within a certain time limit of the first
 >>>change. >>> I >>>This would be useful if you're not using history lists and allow users I >>>to repeat passwords often. It would stop people who would change their C >>>passwords and then immediately change them back to the original, & >>>thereby keeping their old password. >>: >>On certain operating systems from the Pacific Northwest,7 >>I believe one can change the password enough times to ; >>overflow the password history space and cause the desired 4 >>password to fall off the end and thus be reusable. >>  I Mea culpa. I snipped point (iv) from my quote, but had thought that (iv)  $ would catch the minimum requirement:  7 (i) protects passwords from unauthorized disclosure and <     modification when stored and transmitted; (ii) prohibits?     passwords from being displayed when entered; (iii) enforces ;     password minimum and maximum lifetime restrictions; and ;     (iv) prohibits password reuse for a specified number of      generations.  @ >>VMS prevents that attack cold by requiring generated passwords@ >>at that point, but lesser operating systems don't seem to have >>figured it out.  >  > B > For US Federal Government systems, one should call that superiorE > VMS mechanism a "compensating control" if anyone asks about minimum F > password lifetimes.  The term "compensating control" is described inE > great detail in the documents, but basically it means what it says.   - That clears up my misunderstanding thank you.    ------------------------------  $ Date: Sun, 2 Oct 2005 18:08:30 +0100! From: "John" <r.@9999yahoo.co.uk> # Subject: Install a Printer on VMS Q 0 Message-ID: <guU%e.16550$R5.1251@news.indigo.ie>  E How can I install a printer using VMS on an Alpha server. I have the  J following code which I notepaded from the last time one was installed and M have changed the relevany name of printer and its IP address to what I want.  G Name of Printer = OKI , IP Address = 10.1.1.250. Which is a Dot Matrix.   H If I carry out the instructions below will it work or will I cock up my M whole server?? Do I have to add a Print Queue etc .I'm not in IT but want to  I learn something which should be learanable. I can get to the $ prompt etc    Thanks         $UCX  ! UCX> SET HOST OKI/ADDR=10.1.1.250   
 UCX>  exit   $ MC UCX$LPRSETUP        UCX Printer Setup Program       ) Command  < add delete view help exit >: A   ( Adding printer entry, type '?' for help.       Enter printer name to add : OKI   : Enter the FULL name of one of the following printer types:   remote local : remote    Enter printer synonym:  1 Enter full file specification for spool directory   8 SPOOLER DIRECTORY 'sd' :  [SYS$SPECIFIC:[UCX_LPD.OKI]] ?  - Set LPD PrintServer extensions flag 'ps' [] ?   % Set remote system name 'rm' [] ?  oki   ( Set remote system printer name 'rp' [] ?  A Set printer error log file 'lf' [SYS$SPECIFIC:[UCX_LPD]OKI.LOG] ?   @ Enter the name of the printcap symbol you wish to modify.  Other   valid entry is :  )         'q'     to quit (no more changes)   & The names of the printcap symbols are:      #  sd for the printer spool directory   "  lf for the printer error log file  %  lp for the name of the local printer   +  ps for the LPD PrintServer extensions flag   #  rm for the name of the remote host   &  rp for the name of the remote printer    fm for the printer form field    pa for the /PASSALL flag     nd for the /NODELETE flag    cr for the cr  flag  +  p1-p8 for the /PARAMETER=(p1,...,p8) field            Enter symbol name: cr   ) Enter a new value for symbol 'cr'?  [] on   ) New 'cr' is 'on', is this correct?  [y] y    Enter symbol name: q      '                     Symbol  type  value   '                     ------  ----  -----   ? Error log file    :  lf     STR   /SYS$SPECIFIC/UCX_LPD/OKI.LOG   % Printer Queue     :  lp     STR   OKI    PS extensions flag:  ps     STR   % Remote Host       :  rm     STR   oki    Remote Printer    :  rp     STR   ; Spool Directory   :  sd     STR   /SYS$SPECIFIC/UCX_LPD/OKI   $ cr  flag          :  cr     BOOL  on      2 Are these the final values for printer OKI ? [y] y      D Adding comments to printcap file for new printer, type '?' for help.  : Do you want to add comments to the printcap file [n] ? : n      < Do you want the queue to default to print flag pages [y] : n      5 Do you want this procedure to start the queue [n] : y    Creating execution queue: OKI    Updating UCX$LPD_STARTUP.COM   Updating UCX$LPD_SHUTDOWN.COM               7         ***********************************************   7         * UCX$LPD_STARTUP.COM     UCX$LPD_PRINTCAP    *   7         *    and   UCX$LPD_SHUTDOWN.COM               *   7         *  have been updated for this printer         *   7         *                                             *   7         * Set up activity is complete for this printer*   7         ***********************************************           ) Command  < add delete view help exit >: e       ' $ create/dir sys$specific:[ucx_lpd.oki]    $           ------------------------------  % Date: Sun, 02 Oct 2005 00:19:40 -0600 + From: Mark Berryman <mark@theberrymans.com>  Subject: Re: Pipe & MySQL % Message-ID: <433f198e$1@mvb.saic.com>    issinoho wrote:  > Here's a challenge...  > I > When loading a database schema into MySQL on platforms such as Linux &  H > Windows, the usual format is to redirect a SQL text file to the MySQL  > interpreter as follows,  > . >     mysql -u username -p database < file.sql > K > at which point it challenges the user for their password, and if correct   > the SQL file is processed. > K > I am trying to do this on VMS but with no luck. I've tried the following,  > 5 >     $ pipe mysql -u username -p database < file.sql  > K > Both on the command line and in a DCL file with the password on the next   > line.  > G > So far I've been defeated; the password challenge seems to throw the  K > piping process. This is a really useful technique - can anyone help with   > this.   C If its okay to put the password on the command line, the following  
 syntax works:   @ $ pipe mysql -u username --password=password database < file.sql  H If you must prompt for the password, I have found the following to work:  4 $ mysql -u username -p -e "source file.sql" database  
 Mark Berryman    ------------------------------  % Date: Sun, 02 Oct 2005 10:44:01 +0100 # From: issinoho <issinoho@gmail.com>  Subject: Re: Pipe & MySQL 4 Message-ID: <dhoa56$3bf$1$8300dec7@news.demon.co.uk>   Mark Berryman wrote: > issinoho wrote:  >  >> Here's a challenge... >>J >> When loading a database schema into MySQL on platforms such as Linux & I >> Windows, the usual format is to redirect a SQL text file to the MySQL   >> interpreter as follows, >>/ >>     mysql -u username -p database < file.sql  >>D >> at which point it challenges the user for their password, and if % >> correct the SQL file is processed.  >>L >> I am trying to do this on VMS but with no luck. I've tried the following, >>6 >>     $ pipe mysql -u username -p database < file.sql >>G >> Both on the command line and in a DCL file with the password on the  
 >> next line.  >>H >> So far I've been defeated; the password challenge seems to throw the G >> piping process. This is a really useful technique - can anyone help  
 >> with this.  >  > E > If its okay to put the password on the command line, the following   > syntax works:  > B > $ pipe mysql -u username --password=password database < file.sql > J > If you must prompt for the password, I have found the following to work: > 6 > $ mysql -u username -p -e "source file.sql" database >  > Mark Berryman    Thank-you. That *does* work.  E Shame though that the pipe redirection has problems not evidenced on   other platforms.   ------------------------------  $ Date: Sun, 2 Oct 2005 09:43:12 -0400' From: "Main, Kerry" <Kerry.Main@hp.com> # Subject: RE: Time to produce EV79s! R Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB70C010@tayexc19.americas.cpqcorp.net>   > -----Original Message-----9 > From: JF Mezei [mailto:jfmezei.spamnot@teksavvy.com]=20  > Sent: October 2, 2005 1:06 AM  > To: Info-VAX@Mvb.Saic.Com % > Subject: Re: Time to produce EV79s!  >=20 > "Main, Kerry" wrote:B > > > > HP has not "extended" PA-RISC. The 8900 has been announced > > > as the end of $ > > > > the line for that processor. > > > % > > > As was the 8800 and the 8700...  >=20 > > 8800=3D1Ghz  > > 8900=3D1.1Ghz  >=20 >=20D > They were still extensions to the PaRisc product life because IA64G > wasn't ready to take on serious jobs and now because customers aren't > > adopting IA64 like HP and Intel would have wanted them to=20 > abandon PaRisc > and jump into IA64.  >=20  E JF - the 8900 was an eol enhancement in the same manner that EV7x was  for the Alpha line.   ; > The difference here is that HP sees HP-UX as strategic=20  > (still) and willG > do what it takes to retain customers, even it it means producing more ? > PARiscs at higher speeds and keeping PaRisc alive for longer.   F HP would like both PA-RISC and Alpha Cust's to move to PA-RISC as soonD as they can, but at a time when it makes sense for the Customer. For? some Cust's with performance sensitive environments, this small H enhancement might buy them a bit of time to better prepapre for the moveH to Intanium sewrvers in the same manner as the EV7x enhancement bought a. little more time for those in the Alpha world.   >=20; > For VMS, HP doesn't care and still wants to kill Alpha=20  > products ASAP and H > force customers to abandon 64 bit and move to emulated VAX with Charon@ > vax on 8086s. And as you know, HP doesn't even have to huts=20
 > to formally A > announce its decision to no longer produce VAX versions of VMS.  >=20  @ My view that I recommend to OpenVMS Cust's looking at a platform? migration is that there are pro's-n-con's with each option, but  generally speaking:   . 1. The best approach is to do native ports.=20B 2. If there is a reason why a native port is not possible, then anG emulator on the original OS platform (VAX emulator on OpenVMS Alpha) is  the next best option.=20F 3. If neither 1 or 2 is feasible, then an emulator on the x86 platform is the next best option.=20    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: Sun, 2 Oct 2005 10:02:50 -0400' From: "Main, Kerry" <Kerry.Main@hp.com> # Subject: RE: Time to produce EV79s! R Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB70C012@tayexc19.americas.cpqcorp.net>   > -----Original Message----- > From: Main, Kerry=20 > Sent: October 2, 2005 9:43 AM  > To: Info-VAX@Mvb.Saic.Com % > Subject: RE: Time to produce EV79s!  >=20 >=20 > > -----Original Message-----; > > From: JF Mezei [mailto:jfmezei.spamnot@teksavvy.com]=20 ! > > Sent: October 2, 2005 1:06 AM  > > To: Info-VAX@Mvb.Saic.Com ' > > Subject: Re: Time to produce EV79s!  > >=20 > > "Main, Kerry" wrote:D > > > > > HP has not "extended" PA-RISC. The 8900 has been announced > > > > as the end of & > > > > > the line for that processor. > > > > ' > > > > As was the 8800 and the 8700...  > >=20 > > > 8800=3D1Ghz  > > > 8900=3D1.1Ghz  > >=20 > >=20F > > They were still extensions to the PaRisc product life because IA64; > > wasn't ready to take on serious jobs and now because=20  > customers aren't@ > > adopting IA64 like HP and Intel would have wanted them to=20 > > abandon PaRisc > > and jump into IA64.  > >=20 >=20G > JF - the 8900 was an eol enhancement in the same manner that EV7x was  > for the Alpha line.  >=20= > > The difference here is that HP sees HP-UX as strategic=20  > > (still) and will= > > do what it takes to retain customers, even it it means=20  > producing moreA > > PARiscs at higher speeds and keeping PaRisc alive for longer.  >=20H > HP would like both PA-RISC and Alpha Cust's to move to PA-RISC as soonF > as they can, but at a time when it makes sense for the Customer. ForA > some Cust's with performance sensitive environments, this small @ > enhancement might buy them a bit of time to better prepapre=20 > for the move8 > to Intanium sewrvers in the same manner as the EV7x=20 > enhancement bought a0 > little more time for those in the Alpha world. >=20	 [snip...]   ? Ooops big typo in my previous reply .. That's what you get when @ responding before Tim Hortons coffee is not fully consumned yet.  H > HP would like both PA-RISC and Alpha Cust's to move to PA-RISC as soonE > as they can, but at a time when it makes sense for the Customer.=20    Should have read:   H HP would like both PA-RISC and Alpha Cust's to move to Integrity serversH as soon as they can, but at a time when it makes sense for the Customer.   :-)    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. =20    ------------------------------  % Date: Sun, 02 Oct 2005 10:49:23 +0100 # From: issinoho <issinoho@gmail.com>  Subject: Re: Vamp Hacked! 4 Message-ID: <dhoaf6$3to$1$8302bc10@news.demon.co.uk>   Larry Kilgallen wrote:\ > In article <dhm83f$bh7$1$830fa7a5@news.demon.co.uk>, issinoho <issinoho@gmail.com> writes: >  >>Larry Kilgallen wrote: >>] >>>In article <dhljot$s2r$1$830fa17d@news.demon.co.uk>, issinoho <issinoho@gmail.com> writes:  >>>  >>>  >>> K >>>>WHile you are there, do you know how compliant (if at all) some of the   >>>>PHP extensions are?  >>>  >>>  >>>Compliant with what ? >>>  >>>  >>> . >>>>I've tried to load Drupal which needs the K >>>>php_session extension. Doesn't work AT ALL. Similarly, vBulletin needs  3 >>>>the php_xml extension - again complete failure.  >>>>( >>>>Who do I talk to about these issues? >>>  >>> 2 >>>The vendor who sold you the PHP implementation. >>1 >>Threads like this frustrate the hell out of me.  >  > C > Consider those of us who have not seen the answer to the question  > "Compliant with what ?". >  >  >>It seems impossible to  J >>ask a simple question without half a dozen people ripping you to shreds A >>with unhelpful responses largely composed of pedantic minutiae.  >>- >>Look, HP kindly offer free versions of PHP  K >>(http://h71000.www7.hp.com/openvms/products/ips/apache/csws_php.html); I  K >>have chosen to utilise said product in an effort to provide a service to  2 >>the community. I am simply asking for some help. >  > D > "Who do I talk to about this issue?" sounds very much like you areG > looking for support.  If you got "free software" you are on your own.   I Does the word "community" mean anything to you? Surely we are all trying   to help each other. No?    ------------------------------  $ Date: Sun, 2 Oct 2005 07:42:22 -0500( From: Wayne Sewell <wayne@tachysoft.com> Subject: Re: Vamp Hacked! / Message-ID: <00A4AAAD.49B74AD0.1@tachysoft.com>   . >From: Kilgallen@SpamCop.net (Larry Kilgallen) >X-Newsgroups: comp.os.vms >Subject: Re: Vamp Hacked!  >Date: 2 Oct 2005 00:23:37 -0500 >Organization: LJK Software 
 >Lines: 32  [ >In article <00A4A9E5.AA2FE8E5.1@tachysoft.com>, Wayne Sewell <wayne@tachysoft.com> writes: 0 >>>From: Kilgallen@SpamCop.net (Larry Kilgallen) >>   >>>> or bugtracking systems, >>> F >>>PTR (not yet released to freeware, but contact Steve Hoffman if you >>>     have a serious need) >>>  >>  J >> Accessible via a web browser from anywhere on the internet?  The people > ? >Accessible via a web browser via HTTP.  Or by Mail, or by DCL. G >What you allow is up to you.  "Anywhere on the Internet" is up to you.   P Okay.  However, packages that are not available are not relevant.  I do not knowO the qualifications for "serious need".  Surely anyone developing software to be M distributed to others, whether commercial or free, has a "serious need" for a  bugtracking system.     J I was just happy to find a multi-site bugtracker that could run on vms, asL opposed to a eunuchs machine (bugzilla) or a never-to-be-sufficiently-damnedM billybox.  If I can replace it with this native-vms PTR, I will.  If I can't, ) there is no point in even mentioning PTR.   O If there were more vms software vendors, it would be worthwhile to develop such M a system for sale, or at least as shareware.  However, with the current state 
 of things ...    Wayne 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: 2 Oct 2005 08:31:35 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen)  Subject: Re: Vamp Hacked! 3 Message-ID: <PCWicgpjLlTE@eisner.encompasserve.org>   Z In article <00A4AAAD.49B74AD0.1@tachysoft.com>, Wayne Sewell <wayne@tachysoft.com> writes:/ >>From: Kilgallen@SpamCop.net (Larry Kilgallen)   \ >>In article <00A4A9E5.AA2FE8E5.1@tachysoft.com>, Wayne Sewell <wayne@tachysoft.com> writes:1 >>>>From: Kilgallen@SpamCop.net (Larry Kilgallen)  >>>  >>>>> or bugtracking systems,  >>>>G >>>>PTR (not yet released to freeware, but contact Steve Hoffman if you  >>>>     have a serious need)  >>>> >>> K >>> Accessible via a web browser from anywhere on the internet?  The people  >>@ >>Accessible via a web browser via HTTP.  Or by Mail, or by DCL.H >>What you allow is up to you.  "Anywhere on the Internet" is up to you. > R > Okay.  However, packages that are not available are not relevant.  I do not knowQ > the qualifications for "serious need".  Surely anyone developing software to be O > distributed to others, whether commercial or free, has a "serious need" for a  > bugtracking system.     K I think so too.  I imagine Steve Hoffman does, but he might not be inclined J to comment in public.  Certainly in making internal requests for releasing- PTR he would feel free to make such comments.   L > I was just happy to find a multi-site bugtracker that could run on vms, asN > opposed to a eunuchs machine (bugzilla) or a never-to-be-sufficiently-damnedO > billybox.  If I can replace it with this native-vms PTR, I will.  If I can't, + > there is no point in even mentioning PTR.   G The point in mentioning PTR is that you have a more serious need for it I right now than I do.  One does not expect VMS Development to assign staff E to create features for which there is not a serious need.  Similarly, H I do not expect Steve Hoffman to assign himself the task of fighting the2 bureaucracy dragon unless there is a serious need.  E I have seen PTR and I am quite impressed.  There is a lot of software  that does not impress me.   Q > If there were more vms software vendors, it would be worthwhile to develop such O > a system for sale, or at least as shareware.  However, with the current state  > of things ...   F My point is that DEC already developed such software, but they did not' see any more market for it than you do.    ------------------------------  # Date: Sun, 02 Oct 2005 13:46:32 GMT ( From: Alan Greig <greigaln@netscape.net>' Subject: Re: [OT] - dealing with ;32767 = Message-ID: <YwR%e.45855$iW5.24748@fe3.news.blueyonder.co.uk>    Larry Kilgallen wrote:  E > The recently release US Federal Government NIST SP 800-53 has a set H > of rules that would avoid such malfeasance.  I hope it will be adopted% > by the HIPPA/SOX/GLB crowd as well.   G I've only said the least of it in a public posting. No backups had run  I for several months at least on the main cluster and several years on one  A system. Site documentation makes no reference to VMS backups and  H basically consists solely of "If phone call complains of X then SET DEF I somewhere, @something_restart" this to be typed in by support staff with  G no VMS knowledge. One of an HSJ40 pair is sitting dismantled on top of  C the array and dual redundant power to the shelves disconnected. No  A spareset disks left and errors starting to mount on some devices.   G Old versions of Oracle installed with the old Oracle default passwords  H to fully privileged VMS accounts. Another cluster 500 miles away, which D I was told no longer existed, must be a ghost then as I've found it D backing up 1GB of data every day over the DECNET WAN. A very active H ghost as I was able to set host into it and find a priv password for it > in a DECNET "user pass" string buried in a local command file.  I Specialist Dialogic kit installed means that these VMS systems control a  F major part of a telephone exchange for a large call centre as well as B running the Oracle backup of the associated financial (stocks and  shares) database.   I Site documentation actually says "ignore the warning about failed fan if  D booting this system and hit C at SYSBOOT> prompt". Well that worked F until it cooked a few weeks ago. I am told there is a firmware bug in E early ES40s that allowed the machine to run with certain failed fans  / combinations that should not have been allowed.   C If a node fell over permanently an Oracle DBA with just enough VMS  H knowledge to move the database and SQL/Net services to another node was H usually drafted in. Of course the systems have been supposedly close to H retirement for years but that is no excuse for the state they were left 5 in by the household name outsourced service provider.   G Oh yes SHOW/QUEUE/ALL/FULL finds print jobs "retained on error" dating  ) back to 1998. And I could go on and on...   G At most of my previous workplaces I would have been sacked on the spot  I at a site audit as would the site director for allowing stuff like this.  (   I am truly shocked at what I've found. --  
 Alan Greig   ------------------------------   End of INFO-VAX 2005.550 ************************                                                                                                                                                                                                                                                                                                                                  RT 194,116,244,16,13,2015 >>> 200 Port 13.20 at Host 194.116.244.16 accepted. <<< RETR delete_all.comdZ >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/delete_all.com (3828 bytes) started.: >>> 226 Transfer completed.  3236 (8) bytes transferred. <<< PORT 194,116,244,16,13,21a5 >>> 200 Port 13.21 at Host 194.116.244.16 accepted.e <<< RETR grand_tots.comoZ >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/grand_tots.com (2386 bytes) started.: >>> 226 Transfer completed.  1642 (8) bytes transferred. <<< PORT 194,116,244,16,13,22o5 >>> 200 Port 13.22 at Host 194.116.244.16 accepted.d <<< RETR login.comU >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/login.com (1692 bytes) started.f: >>> 226 Transfer completed.  1318 (8) bytes transferred. <<< PORT 194,116,244,16,13,2315 >>> 200 Port 13.23 at Host 194.116.244.16 accepted.d <<< RETR old_b.comU >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/old_b.com (1446 bytes) started. 9 >>> 226 Transfer completed.  570 (8) bytes transferred.  <<< PORT 194,116,244,16,13,24 5 >>> 200 Port 13.24 at Host 194.116.244.16 accepted.  <<< RETR submit.txt5V >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/submit.txt (4982 bytes) started.: >>> 226 Transfer completed.  4105 (8) bytes transferred. <<< PORT 194,116,244,16,13,2505 >>> 200 Port 13.25 at Host 194.116.244.16 accepted.E <<< RETR tapecopy.history ] >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/tapecopy.history (29610 bytes) started.l; >>> 226 Transfer completed.  28071 (8) bytes transferred., <<< PORT 194,116,244,16,13,26o5 >>> 200 Port 13.26 at Host 194.116.244.16 accepted. <<< RETR tctree.lisoW >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/tctree.lis (40660 bytes) started.d; >>> 226 Transfer completed.  39100 (8) bytes transferred.2 <<< PORT 194,116,244,16,13,2715 >>> 200 Port 13.27 at Host 194.116.244.16 accepted.  <<< RETR tctreeproc.lis [ >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/tctreeproc.lis (24834 bytes) started.t; >>> 226 Transfer completed.  22253 (8) bytes transferred., <<< PORT 194,116,244,16,13,28o5 >>> 200 Port 13.28 at Host 194.116.244.16 accepted. <<< RETR template.rno X >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/template.rno (1434 bytes) started.9 >>> 226 Transfer completed.  582 (8) bytes transferred., <<< PORT 194,116,244,16,13,29o5 >>> 200 Port 13.29 at Host 194.116.244.16 accepted.  <<< RETR tree.seqrU >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/tree.seq (14132 bytes) started.n; >>> 226 Transfer completed.  13389 (8) bytes transferred.4 <<< PORT 194,116,244,16,13,32t5 >>> 200 Port 13.32 at Host 194.116.244.16 accepted.m <<< RETR treesize.comGX >>> 150 IMAGE retrieve of /disk$misc/decus/91bvaxlt/treesize.com (2910 bytes) started.: >>> 226 Transfer completed.  2107 (8) bytes transferred. <<< PORT 194,116,244,16,13,33t5 >>> 200 Port 13.33 at Host 194.116.244.16 accepted.e <<< RETR treetape.comeX >>> 150 IMAGE retrieve of /d