Oh, yeah?
Thats a shame, I have been using it for 20+ years, or as long as I can remember....Not documented IIRC, nor in the helps, BUT there it is...
RELEASE: C.75.00 MPE/iX HP31900 C.45.05 USER VERSION: C.75.00
:ksamutil
HP32208A.07.04 THU, NOV 29, 2007, 5:23 PM KSAMUTIL VERSION:A.07.02
>BUILD KPARTNx;REC=10,10,F,BINARY;DISC=24000;KEYFILE=KKPARTNx;&
>KEY=BYTE,1,10,,DUP;KEYENTRIES=24000;reuse <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
KPARTNX.TEST.STOCK2K & KKPARTNX ARE CREATED.
>v kpartnx
WHICH (1=FILE INFO, 2=KSAM PARAMETERS, 3=KSAM CONTROL, 4=ALL)?4
KPARTNX.TEST.STOCK2K CREATOR=MGR
FOPTIONS(006001)=KSAM, NO :FILE, NOCCTL, F, FILENAME, BINARY, PERM
AOPTIONS(000400)=DEFAULT, NOBUF, DEFAULT, NO FLOCK, NO MR, IN
RECSIZE:SUB:TYP:LDNUM:DRT:UN.: CODE:LOGICAL PTR: END OF FILE:FILE LIMIT
10: 8: 3: 1: 8: 0: 0: 0: 0: 24000
LOG. COUNT:PHYS. COUNT:BLK SZ:EXT SZ:NR EXT: LABELS:LDN: DISCADDR:
1: 0: 100: 235: 8: 0:
0:00000000000:
KEY FILE=KKPARTNX KEY FILE DEVICE=1 SIZE= 3442 KEYS= 1
FLAGWORD(000010)=RANDOM PRIMARY, FIRST RECORD=0, PERMANENT, REUSE <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
KEY TY LENGTH LOC. D KEY BF LEVEL
1 B 10 1 Y 112 1
DATA FILE = KPARTNX VERSION= A.7.4
KEY CREATED=333/'07 17:16:24.8 KEY ACCESS= 333/'07 17:16:34.4
KEY CHANGED=333/'07 17:16:24.8 COUNT START=333/'07 17:16:24.8
DATA RECS = 0 DATA BLOCKS= 0 END BLK WDS= 0
DATA BLK SZ= 100 DATA REC SZ= 20 ACCESSORS= 0
FOPEN 1 FREAD 0 FCLOSE 1
FREADDIR 0 FREADC 0 FREADBYKEY 0
FREMOVE 0 FSPACE 0 FFINDBYKEY 0
FGETINFO 0 FGETKEYINFO 0 FREADLABEL 0
FWRITELABEL 0 FCHECK 0 FFINDN 0
FWRITE 0 FUPDATE 0 FPOINT 0
FLOCK 0 FUNLOCK 0 FCONTROL 0
FSETMODE 0 FREE KEYBLK 0 FREE RECS 0
KEYBLK READ 2 KEYBLK WRITTEN 0 KEYBLK SPLIT 0
KEY FILE EOF 10 FREE KEY HD 0 SYSTEM FAILURE 0
MIN PRIME 0 MAX PRIME 0 RESET DATE
DATA FIXED TRUE DATA B/F 10 TOTAL KEYS 1
FIRST RECNUM 0 MIN RECSIZE 10 LANG NATIVE-3000
WHICH (1=FILE INFO, 2=KSAM PARAMETERS, 3=KSAM CONTROL, 4=ALL)?
________________________________________
From: Duane Percox [[log in to unmask]]
Sent: Thursday, 29 November 2007 1:33 PM
To: John Pitman
Subject: RE: [HP3000-L] COPY command and File access issue
cm ksam uses ksamutil to manage ksam files
ksamutil build has no reuse parm
I think you are thinking of ksam/xl (nm ksam) which uses
the build command and has the reuse parm.
duane
> -----Original Message-----
> From: [log in to unmask]
> [mailto:[log in to unmask]] On Behalf Of John Pitman
> Sent: Wednesday, November 28, 2007 5:05 PM
> To: [log in to unmask]
> Subject: RE: [HP3000-L] COPY command and File access issue
>
>
> I seem to recall cm ksam having a ;reuse parm on the build
> command? ________________________________________
> From: HP-3000 Systems Discussion [[log in to unmask]] On
> Behalf Of Dale Pepoon [[log in to unmask]]
> Sent: Thursday, 29 November 2007 9:23 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] COPY command and File access issue
>
> CM KSAM did not allow the reuse of deleted records and this
> process was necessary it there is a high volume of adds and
> deletes. KSAM XL now allows the reuse of deleted records.
> This may be a hold over from the MPEV days......
>
> Therefore:
> This step may not be necessary if :
> a. performance is not a problem and
> b. chronological order of the records is not required.
>
> Thanks
> dp
>
>
>
>
> Dale Pepoon/MIS/Circuit City
> 11/28/2007 04:40 PM
>
> To
> "Rao, Raghu" <[log in to unmask]>
> cc
> [log in to unmask]
> Subject
> Re: [HP3000-L] COPY command and File access issue
>
>
>
>
>
> Sorry to say but
> Remove all deleted transaction records.
> is exactly what it is doing...........more later..
>
> If any process is accessing this file you will not be able to
> perform this process. Notice it actually purges the DIVTRAN file.
>
> This is a KSAM file. When a record is deleted from a KSAM
> file it does not really delete the record. It just steps on
> some part of the record marking it as deleted. (Help me out
> someone... I think it is the first
> byte.)
>
> Here is the code with my comments.....
> !# Back up the whole file
> !COPY DIVTRAN.DATA,DIVTRANA.DATA
> !# did the back up work
> :IF CIERROR = 0
> !# Fcopy only the non deleted records
> ! FCOPY FROM=DIVTRAN.DATA;TO=(DIVTRANB.DATA)
> !# Purge the original file
> ! PURGE DIVTRAN.DATA
> !#Rename the new file that has no deleted records as the
> original file for tomorrows processing
> ! RENAME DIVTRANB.DATA,DIVTRAN.DATA
> !#Everything worked OK so lets purge the backup
> ! PURGE DIVTRANA.DATA
> !endif
>
> I think that KSAM files do not reuse deleted records. If
> this process does not happen periodically the file will fill
> up even when there are no records in the file.
>
> I do not know anything about AMISYS ... but I would not run
> this piece of code while people are accessing this file.....
>
> Thanks
> dp
>
>
>
>
>
> "Rao, Raghu" <[log in to unmask]>
> Sent by: HP-3000 Systems Discussion <[log in to unmask]>
> 11/28/2007 04:15 PM Please respond to "Rao, Raghu"
> <[log in to unmask]>
>
>
> To
> [log in to unmask]
> cc
>
> Subject
> [HP3000-L] COPY command and File access issue
>
>
>
>
>
>
> Hi all,
>
> We have a job that runs twice daily, once at 12 noon and the
> other at 8:30 nightly. The job runs fine on the nightly
> schedule without any issues, but the same job throws up a
> CIERROR 9135 on a COPY statement because the particular file
> is being accessed during day time. I have the following questions :
>
> 1) If the file was not being accessed, then what are the
> series of statements inside the IF - ENDIF trying to do ?
> Please do not reply back stating "Remove all deleted
> transaction records"
>
> 2) Is there a way to issue a COPY or FCOPY statement even if
> the file is being accessed ?
>
> 3) This job is a standard Amisys job MEP0300. Does any other
> Amisys customers out there think this job should not be
> running during the day time ?
>
>
> NIGHTLY JOB RUN STDLIST :
>
> 218 :COMMENT
> *************************************************************
> 219 :COMMENT ** Remove all deleted transaction records.
> **
> 220 :COMMENT
> *************************************************************
> 221 :
> 222 :SETJCW CIERROR,0
> 223 :CONTINUE
> 224 :COPY DIVTRAN.DATA,DIVTRANA.DATA
> 225 :IF CIERROR = 0
> 226 *** EXPRESSION TRUE
> 227 : FCOPY FROM=DIVTRAN.DATA;TO=(DIVTRANB.DATA)
> 228
> 229 HEWLETT-PACKARD 31900A.05.04 FILE COPIER TUE, NOV 27, 2007,
> 8:32 PM
> 230 (C) HEWLETT-PACKARD CO. 1999
> 231 *143*
> 232 WARNING: FROMFILE IS EMPTY
> 233 0 RECORDS PROCESSED *** 0 ERRORS
> 234
> 235 END OF SUBSYSTEM
> 236 : PURGE DIVTRAN.DATA
> 237 : RENAME DIVTRANB.DATA,DIVTRAN.DATA
> 238 : PURGE DIVTRANA.DATA
> 239 :ENDIF
> 240 :LISTF [log in to unmask],2
> 241
> 242 TUE, NOV 27, 2007, 8:32 PM
> 243 ACCOUNT= AMISYS GROUP= DATA
> 244
> 245 FILENAME CODE ------------LOGICAL RECORD-----------
> ----SPACE----
> 246 SIZE TYP EOF LIMIT
> R/B SECTORS
> #X MX
> 247
> 248 DIVTRAN 84B FAK 0 1000
> 46 320
> 2 *
> 249
> 250
>
> DAYTIME JOB RUN STDLIST :
>
> 218 :COMMENT
> *************************************************************
> 219 :COMMENT ** Remove all deleted transaction records.
> **
> 220 :COMMENT
> *************************************************************
> 221 :
> 222 :SETJCW CIERROR,0
> 223 :CONTINUE
> 224 :COPY DIVTRAN.DATA,DIVTRANA.DATA
> 225 ^
> 226 COPY command cannot open the source file. (CIERR 9135)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 227 :IF CIERROR = 0
> 228 *** EXPRESSION FALSE: COMMANDS IGNORED UNTIL MATCHING
> ELSEIF/ELSE
> 229 /ENDIF
> 230 : FCOPY FROM=DIVTRAN.DATA;TO=(DIVTRANB.DATA)
> 231 : PURGE DIVTRAN.DATA
> 232 : RENAME DIVTRANB.DATA,DIVTRAN.DATA
> 233 : PURGE DIVTRANA.DATA
> 234 :ENDIF
> 235 *** RESUME EXECUTION OF COMMANDS
> 236 :LISTF [log in to unmask],2
> 237
> 238 WED, NOV 28, 2007, 12:01 PM
> 239 ACCOUNT= AMISYS GROUP= DATA
> 240
> 241 FILENAME CODE ------------LOGICAL RECORD-----------
> ----SPACE----
> 242 SIZE TYP EOF LIMIT
> R/B SECTORS
> #X MX
> 243
> 244 DIVTRAN * 84B FAK 3 1000
> 46 320
> 2 *
> 245
> 246
>
> Thanks in advance for your kind replies.
>
> With Best Regards from
> Raghu Rao
>
>
> Confidentiality Notice:
> The information contained in this electronic message is
> intended for the exclusive use of the individual or entity
> named above and may contain privileged or confidential
> information. If the reader of this message is not the
> intended recipient or the employee or agent responsible to
> deliver it to the intended recipient, you are hereby notified
> that dissemination, distribution or copying of this
> information is prohibited. If you have received this
> communication in error, please notify the sender immediately
> by telephone and destroy the copies you received.
>
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
