RE: Single level store & record blocking on update files (was RE:Where is IBM?)

["jt" <jt@xxxxxx>]

| -----Original Message-----
| [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Dan
| Sent: Thursday, April 24, 2003 11:22 AM

| If you can prove to me that the AS/400 supports record blocking
| for update files, even if limited
| to those files with no unique keyed APs, I will buy you lunch.
| (How does White Castle sound? <g>)

(Jes pokin head in here fer a sec, as the feeble number of billable hours
only pays for a PORTION of the bills, so even though I'm not Doug I'll step
UP to THIS challenge...;-)

     Frtatestpf uP   e             disk

     C                   eval      rttxt = 'wassup?'
     C                   update    rtatestr

Btw, PLEASE do not start up the Primary Cycle debate, as I'm still
recovering from a prior War (the War of 2001)...!  I dunno why your example
doesn't block, and forget whether the above blocks at OS or compiler level.
(Do it matter?)

The message you're getting is one-a the older ones in CPF/OS/400, so it
provides (iirc) an excellent level of detail on the second-level MSGTXT,
Dan, with a reason code why it was changed to SEQONLY(*YES).