RE: INZPFM replacement ???

["Walden H. Leverich III" <WaldenL@xxxxxxxxxxxxxxx>]

Fair (and true) enough, but... Why, in what is obviously relatively new code
-- as evidenced by the use of %Error and the (e) extender -- would use use
such a technique? RRN access seems to me to be older that the darn cycle <G>

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
 

-----Original Message-----
From: Ken.Slaugh@xxxxxxxxxx [mailto:Ken.Slaugh@xxxxxxxxxx] 
Sent: Wednesday, May 28, 2003 11:20 AM
To: Midrange Systems Technical Discussion
Subject: RE: INZPFM replacement ???



When an RPG program maintains a physical file by RECNO, relative record
number, the RECNO value during the WRITE operation must equal the actual
value of a deleted record to write. RECNO, however cannot be a value beyond
the extent of the file.

Here's some RPG code...

fFileIO    uf a f32766        disk    usropn
f                                     infds($_FileDS)
f                                     recno($DataRRN)

 *  Attempt to retrieve record to update
c                   eval      $DataRRN    = JO$CtrR
c     $DataRRN      chain     FileIO

c                   eval      $Data       = %subst(@JrnRcv: 126)
c                   write(e)  FileIO        $FileDataDS
c                   eval      $Posted     = NOT %Error



Ken Slaugh (707) 795-1512 x118
Chouinard & Myhre, Inc.
CA/400 Certified Specialist
iSeries Network/MSE Administrator
http://www.cm-inc.com/


 

                      "Walden H. Leverich III"

                      <WaldenL@xxxxxxxxxxxxxxx>                         To:
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> 
                      Sent by:                                          cc:

                      midrange-l-bounces+ken.slaugh=cm-inc.com@x
Subject:  RE: INZPFM replacement ???

                      idrange.com

 

 

                      05/28/2003 07:56 AM

                      Please respond to Midrange Systems

                      Technical Discussion

 

 





Just out of curiosity, why would you want to INZPFM a file? I understand
what it does (I think -- it makes a file full of deleted rows) but for what
reason. Many years ago, when disk was scarce and you wanted to make sure
you
had room for x rows, maybe, but today that is seldom a problem.

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


-----Original Message-----
From: Ken.Slaugh@xxxxxxxxxx [mailto:Ken.Slaugh@xxxxxxxxxx]
Sent: Tuesday, May 27, 2003 4:38 PM
To: Midrange Systems Technical Discussion
Subject: INZPFM replacement ???


I submitted this to the RPG group and haven't had much success other
starting a discussion about the INZPFM command itself...

Maybe some cleaver Midrange-L guru can help with an INZPFM replacement.
Here's the post:
----------------------------------------------------------
INZPFM creates records in a physical file member. It can create deleted
records. Can RPG create deleted records?

The WRITE opcode and RECNO are used to write to a particular deleted record
but this technique can NOT append records beyond the extent of the file.
Another issue with INZPFM is that it requires a dedicated file to avoid
LCKW situations.

TIA,

Ken Slaugh (707) 795-1512 x118
Chouinard & Myhre, Inc.
CA/400 Certified Specialist
iSeries Network/MSE Administrator
http://www.cm-inc.com/


_______________________________________________
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.