You shouldn't need the klist on the delete.

From the manual:
"If a search argument (search-arg) is not specified, the DELETE
operation deletes the current record (the last record retrieved). The
record must have been locked by a previous input operation (for
example, CHAIN or READ)."

HTH,
Charles

On Wed, Oct 14, 2009 at 4:02 PM, jmmckee <jmmckee@xxxxxxxxxxxxxx> wrote:
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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].