× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Native files in the 36 Environment
  • From: email@xxxxxxxxxxxxxxxxxxx (James W Kilgore)
  • Date: Tue, 09 Feb 1999 02:03:41 -0800
  • Organization: Progressive Data Systems, Inc.

Sam,

Larry is correct in the overall view of multiformat logical files.  (somehow I 
got
the feeling of "bleeding edge" in his experience)

For Input only processing, a format selector program (FSP) works just dandy.  
Now
the FSP in not rocket science -IF- the file has a unique record identifier per
format.  Like id=1 is header, id=2 is detail, id=3 is total and "id" is a 
defined
field in each record.

Any program that is in use today can use a multiformat logical in place of a
multiformat physical WITHOUT a huge program change.

You are at a crossroad of choosing between multiformat flat files in -need- of a
format selector program or expanding the program(s) to deal with separate 
physical
files. (no 15 file limits here)

IMHO, for the amount of work involved for a format selector (and the testing
involved) one may as well face the reality of single format physicals.  Not 
just for
the sake of the programs in question, but for the added benefit for using these
files to rid yourself of S/36 environment dependency.  A higher short term cost 
with
a lower long term cost.  Oh, I forgot my salesmanship: higher long term benefits
;-)       (always end on the "up" side)

I made an earlier post about "a cause for maintenance is an opportunity to 
upgrade".
Not an original concept, just a repeated thread. Which translates into: its 
overtime
now (once) or overtime again and again, later.  And by the time you're done you 
wind
up where you should have gone in the first place.

Regards,
James W. Kilgore
email@James-W-Kilgore.com






Larry Bolhuis wrote:

> Sam,
>
>   The main problem you need to address is adding records to the file through
> your multi-format logical file.  Since the 36RPG program cannot tell DB2 which
> format it is writing you will need to write a Format Selector Program and 
>assign
> it to the Logical file.  When a 36RPG program writes a record control will 
>pass
> to the FSP. It recieves the file buffer, examines it to determine the correct
> format name and returns it to the database.  No changes are needed in the 
>36RPG
> programs.  One word of caution: You must handle the condition where it cannot 
>be
> determined from the buffer which format is being written.  You must either 
>'pick
> one' (can you say 'bad data') or abnormally terminate the FSP.  If you do not
> return a valid format name the FSP will be called repeatedly forever. (guess 
>how
> I know.)
>
>  - Larry
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.