DALOCK & 7.10.G1

[Hamilton, Allison]

> This issue came up in the fall, and I responded to the person personally,
> and then never had time to finish my investigation and respond to the
> list... finally here's the updated information for DALOCK for anyone who
> needs it.  This information also would be valid for 710F versions as well,
> and probably 710E versions.
> 
> The VMS_LCK structure is the same
> The LCK structure is now size 68, defined as:
> 
> struct LCK {                           /* Powerhouse lock structure
> */
>     struct VMS_LCK lms;         /* VMS lock information           */
>     short int      lck_usg;           /* usage count of this lock block */
>     short int      rec_lck_cnt;     /* Record lock count              */
>     struct {
>       int          lck_vld : 1;          /* Valid lock block
> */
>       int                  : 7;             /* RESERVED
> */
>       int                  : 24;           /* Fill to int 32 boundary.
> */
>       } u_lck_rsv;
>     char           lck_nam[32];     /* lock name                      */
>     char           lck_lvl;              /* Current LMS lock level
> */
>     char           charfill[3];          /* Align to int 32 boundary.
> */
>     } ;
> Allison Hamilton
> 
> ----------
> From: 	Chris Sharman[SMTP:Chris.Sharman@ccagroup.co.uk]
> Sent: 	Thursday, October 22, 1998 10:41 AM
> To: 	Allison.Hamilton@cognos.com
> Cc: 	Chris.Sharman@ccagroup.co.uk
> Subject: 	RE: DALOCK & 7.10.G1
> 
> >I will look at the documentation and compare it with the code this
> weekend,
> >and send you an updated version, hopefully next week.  I think you
> mentioned
> >that you had been talking with Customer Support about this.  It would be
> >extremely helpful if you would ask them to log a bug against your call so
> >that I can keep track of the problem and resolution.Thanks!
> 
> Passed on to liz.latimer
> 
> >I once knew why the SYSLCK was there, but it's been so long...  It may
> have
> >to do with sharing screen global sections across the system for QUICK.
> But
> >that doesn't explain QTP, so that probably isn't it.
> 
> SYSGBL (and a QKGO parameter) control systemwide screen global sections.
> 
> As far as I know the only use for SYSLCK is to allow the lck$m_system flag
> on
> calls to $enq[w], and only new locks at that, not lock conversions. If you
> could
> search the sources for that, that would probably furnish the answer.
> 
> Thanks, Chris
> ______________________________________________________________________
> Chris Sharman			Chris.Sharman@CCAgroup.co.uk
> CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS.
> 
> 
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.