RE: Somewhat simplistic question about record delete

Thank you Sharon and Charles. I deeply appreciate the confirmation. I looked at a previous effort months ago and it did not have the klist on the delete. Something happened then, and it may well have been the includion of the klist on the delete. I don't remember, and from the mess, I am not sure I want to.

John McKee


-----Original message-----
From: "Wintermute, Sharon" Sharon.Wintermute@xxxxxxxxxxxxxxxx
Date: Wed, 14 Oct 2009 15:29:19 -0500
To: "Midrange Systems Technical Discussion" midrange-l@xxxxxxxxxxxx
Subject: RE: Somewhat simplistic question about record delete

Sorry I misunderstood your question.

The answer is not necessarily.

The reade does get the next record in the list, but by using a klist on
the delete it does its own setll and delete. Now if this is only a
partial key this can cause a problem.

For example,

Kfields are: key1, key2, key3.

Your klist is Key1: Key2.

If the record you have has values 1,2,3 and before you can process the
delete, some other process adds record with 1,2,2. The 1,2,2 is the one
that is actually deleted.

In order to verify you are deleting the record you read, you will need
to remove the klist from the delete.


Sharon Wintermute


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of jmmckee
Sent: Wednesday, October 14, 2009 3:03 PM
To: Midrange Systems Technical Discussion
Subject: RE: Somewhat simplistic question about record delete

I was doing testing and found that out. My concern is if I read the
file and identify the record format that was read, does the delete, when
used with the same klist but with the record format, delete the record
just read from the file. I looked through the vendor code and never saw
where the code was doing this. One physical file is the main
information and the second is extended information. I want to think
that a delete of a specific record format after a file read would work.
Just never found an example in the code. Which is somewhat disturbing,
as both files undergo a purge process. Seems that using the LF would be
a logical way to proceed - unless my understanding is incorrect. Thus
my original post. I can't believe I am making this sound as complicated
as it seems to me.

John McKee

-----Original message-----
From: "Wintermute, Sharon" Sharon.Wintermute@xxxxxxxxxxxxxxxx
Date: Wed, 14 Oct 2009 14:30:52 -0500
To: "Midrange Systems Technical Discussion" midrange-l@xxxxxxxxxxxx
Subject: RE: Somewhat simplistic question about record delete

When you do this kind of reade you will need to set 09 and 10 OFF

before

you do the reade. IIRC, it does not do it for you.


Sharon Wintermute

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of jmmckee
Sent: Wednesday, October 14, 2009 1:37 PM
To: Midrange Systems Technical Discussion
Subject: Somewhat simplistic question about record delete

I have a LF with two formats. The two formats are identified by I

specs

that turn on an appropriate indicator when either of the formats is
read.

So, I have this code

xxky setll <filename>
xxky reade <filename>

if *IN09 = *ON
xxky delete <format1>
endif

if *IN10 = *ON
xxky delete <format2>


My simple question is: Is this how the delete is coded for a LF with
multiple formats? I RARELY use delete, as that is usually handled by
the vendor code, but I have a mess to clean up, and don't want to make
it worse.

There is a lot more to the code than the above. I left that out as

the

record selection logic >appears< (over 13000 records to delete) to be
correct. A separate file is supplying the partial key for a loop.


John McKee
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.