Help Required

[Edis, Bob]

Hmmmm, interesting.  Just how many people on this list actually HAVE worked
on Accubanc code?  (I did too!) :)

Blue

-----Original Message-----
From: Witkopp, Richard [mailto:Richard.Witkopp@idt.com]
Sent: Thursday, April 26, 2001 11:34 AM
To: powerh-l@lists.swau.edu
Subject: RE: Help Required


Powerhouse is still popular in England, so there are quite
a few English on the list. You have to make allowances.  :-)

(Keeping head low because he wrote some of that old, nasty
Accubanc code.)

> I thought this was to assist users in clarification of 
> understanding and
> assistance with the powerhouse language not to put down the 
> person submitting
> the question.    Your statement of "Time for you to embark on 
> an education
> program, I think."   was NOT appropriate, "I think" and you 
> must be a very rude
> person.
> 
> The statement was that the program was already written and we 
> are not ready for
> a complete re-write.   You need to completely read the 
> questions, before
> answering in the manner that you did.
> 
> thank you for your input but not your personal comments
> Margaret Johns
> 
> 
> 
> 
> 
> Chris Sharman <Chris.Sharman@ccagroup.co.uk> on 04/26/2001 03:10:07 AM
> 
> To:   Margaret Johns/Contractor/Dallas/AccuBanc@Accubanc
> cc:   Chris.Sharman@ccagroup.co.uk, powerh-l@lists.swau.edu
> 
> Subject:  RE: Help Required
> 
> 
> 
> 
> 
> >We are trying to help the qtp processes that only read and 
> not update the files
> >to run faster and not lock the files that are being accessed.
> 
> USE ** QUIZ **
> 
> >We have found the commands SET LOCK RECORD UPDATE and the 
> SET FILE {filename}
> >OPEN UPDATE SHARE or SET FILE {filename} OPEN READ SEMIEXCLUSIVE.
> 
> As others have said, READ/UPDATE etc describes your access, and
> SHARE/SEMIEXCLUSIVE etc describes the access you're willing 
> for others to have.
> If you say SHARE, you'll pay the RMS record locking overhead. 
> If you say
> SEMIEXCLUSIVE, your QTP won't run at all if there's a Quick 
> screen with the
> file open for update.
> 
> SET LOCK: file locks are Powerhouse specific. There's a 
> module (DALOCK.[A]OBJ)
> which allows you to use Powerhouse locks in your own 3GL 
> programs, but it's my
> contention that Powerhouse locking doesn't work across 
> multiple UIC groups.
> I'd recommend EXCLUSIVE/SEMIEXCLUSIVE/SHARE as alternatives 
> which do work
> across all well-behaved VMS applications without messing with DALOCK.
> 
> Record locks are normal RMS locks. Whether these are taken 
> depends on whether
> the file is shared or not (above), not on what you tell QTP to do.
> 
> >Does anyone know the differences or the best command to use 
> in the qtp programs
> >that are for read only.
> 
> The best command to use for read only is "$ quiz", rather than QTP.
> That said, if you've some reason to use QTP (eg too many 
> output files), the
> best options are:
> 
> If you have no-one updating the file (Quick, QTP, other):
> 
> set file open read [semi]exclusive ; semi to allow other readers.
> This will minimise RMS locking.
> I'll risk disagreeing with Bob: I don't think this gets you 
> write access, it
> just denies it to others.
> 
> If others are updating:
> 
> set file open read share
> 
> Quiz would definitely win in the first case though, and win 
> hugely in the
> second. Time for you to embark on an education program, I think.
> 
> Regards,
> Chris Sharman
> ______________________________________________________________
> _________
> Chris.Sharman@CCAgroup.co.uk       http://www.ccagroup.co.uk/
> CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS.
> 
> 
> --------------------------------------------------------------
> ---------
> 
> Any views expressed in this message are those of the sender and not
> necessarily those of CCA Group.  The unauthorized use, disclosure,
> copying or alteration of this message is forbidden.  The contents of
> this message may be confidential and/or privileged, copyright 
> CCA Group
> and are intended solely for the use of the individual or 
> entity to whom
> they are addressed.  Whilst this message has been scanned, CCA Group
> cannot guarantee that it is virus free or compatible with your systems
> and accepts no responsibility for any loss or damage arising from its
> use. The recipient is advised to run their own anti-virus software. If
> you receive this message in error please contact
> postmaster@ccagroup.co.uk immediately, destroy any copies and 
> delete it
> from your computer systems.
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to 
> powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe" in message body to 
> powerh-l-request@lists.swau.edu
> http://lists.swau.edu/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a 
> subscriber.
> 
> 
> 
> 
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to 
> powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe" in message body to 
> powerh-l-request@lists.swau.edu
> http://lists.swau.edu/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a 
> subscriber.
> 

= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.