HP3000-L Archives

March 2014, Week 3

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: How to lock a KSAMXL file in POWERHOUSE QUICK
From:
"James B. Byrne" <[log in to unmask]>
Reply To:
James B. Byrne
Date:
Fri, 21 Mar 2014 08:57:23 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (76 lines) 
On Thu, March 20, 2014 17:08, Turner, Jill wrote:
> Hi,
>
> Where you have your file equate I think you need it to have SHR:LOCK rather
> than just ;SHR

--->
:FILE ACCTK06D=ACCTK06D.DATA;SHR;BUF=6;GMULTI;LOCK
:QDESIGN

Q D E S I G N   (PowerHouse  8.39.C)
Copyright 2001 COGNOS INCORPORATED
HARTE & LYNE LIMITED

> SCREEN QKRQTACC LOCK FILE
> FILE REQUISITIONS
> GENERATE
> FIELD FILLER OF REQUISITIONS
> FIELD TRANS-IDENT OF REQUISITIONS REQUIRED NOCHANGE
> FIELD LINE-NUMBER OF REQUISITIONS REQUIRED NOCHANGE
> FIELD ACCOUNT-NUMBER OF REQUISITIONS REQUIRED NOCHANGE
> FIELD VENDOR-REFERENCE OF REQUISITIONS REQUIRED NOCHANGE
> FIELD AMOUNT-DISBURSED OF REQUISITIONS
> FIELD AMOUNT OF REQUISITIONS
> FIELD CURRENCY-CODE OF REQUISITIONS
> FIELD EXCHANGE-RATE OF REQUISITIONS
> FIELD TRANS-IDENT-XREF OF REQUISITIONS REQUIRED NOCHANGE
> FIELD STATUS-CODE OF REQUISITIONS
> FIELD DATE-CREATED OF REQUISITIONS
> FIELD USER-ID OF REQUISITIONS
> GO
MODE:F ACTION:F
01 Filler
02 Transaction
03 Line
04 Account Number
05 Vendor Reference
06 Amount Disbursed
07 Amount
08 Currency
09 Exchange Rate
10 Cross Reference
11 Status code
12 Creation date
13 User






Data access error. (REQUISITIONS*01)
THE FILE MUST BE LOCKED BEFORE ISSUING THIS INTRINSIC  (FSERR 179)

Press RETURN to continue.
<---

I have to admit that this has me completely mystified.  This file is used and
updated through QUICK by our accounting system virtually all day long every
workday and has been since the early 1990's.  I cannot for the life of me
understand why I am having this difficulty reading and writing to a simple
KSAMXL file.  Do KSAMXL files require explicit locks in QDESIGN and therefore
also require an explicit PROCEDURE UPDATE?  I cannot recall.


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:[log in to unmask]
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2