Re: SFLLIN keyword

[Simon Coulter <shc@xxxxxxxxxxxxxxxxx>]

On 14/06/2010, at 4:10 PM, John McKay wrote:

> SFLCSRPRG will operate as described within a record format - it will  
> not
> cross over record fromats.  WIth SFLLIN, you are writing a separate  
> record
> format each time.  Also SFLCSRPRG is not allowed with SFLLIN - the  
> compile
> fails.


Oh bugger! I was sure I'd done this but I see the example I had in  
mind is actually a sub-file without SFLLIN. Documentation says:

"The SFLLIN keyword is not allowed in a record that contains the  
SFLCSRPRG."

which is not what they mean because SFLLIN is specified on the SFLCTL  
record and SFLCSRPRG is specified on the SFL record thus the keywords  
are not in the same record and (if reading the documentation  
literally) should be allowed.

I take issue with your comment that SFLLIN writes separate record  
formats. The code writes to the same record format just as it does  
without SFLLIN. It's WSFM that maps the records into multiple columns  
(i.e. multiple columns of records).

> I would not use SFLLIN here.  Instead I would use the SFLSIZ >  
> SFLPAG, and
> protect and non-display the empty fields.  Messy programming, but it
> achieves the result.

Not sure how that would make the cursor move down an input column  
instead of across.

Given the above information I'd probably use DSM to accomplish this.  
Worth experimenting ...

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         OS/400, i5/OS Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
   Fax:   +61 2 6657 8251                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------