[Info-vax] Calling $CREPRC in COBOL

seasoned_geek roland at logikalsolutions.com
Mon Jul 4 10:34:36 EDT 2022


On Sunday, July 3, 2022 at 7:22:57 PM UTC-5, Arne Vajhøj wrote:
> On 7/3/2022 4:05 PM, seasoned_geek wrote: 
> > On Thursday, June 23, 2022 at 9:14:07 AM UTC-5, osuv... at gmail.com wrote: 
> >> On Tuesday, June 21, 2022 at 12:08:21 AM UTC-4, Dave Froble wrote: 
> > At any rate, there is no SQL that will let you put multi-typed 
> > records in a table. The "best" you could hope for is to have the 
> > primary key fields then a BLOB object one had to hack like we did in 
> > BASIC. You would be right back to CVT$% and RSET logic. (Didn't they 
> > drop RSET and LSET from the DEC BASIC specification at some point?)
> Not true. 
> 
> You define a super class and sub classes and your ORM framework 
> transparently stores and retrieved the different classes. 
> 
> That is basic persistence knowledge. Any young developer would 
> know that.

Well, we will ask Dave to post the TOLAS invoice (or order) record layouts for a defunct customer and you create a functioning VAX BASIC program using SQLite along with Superclass and Subclass and post it here.

> > RMS indexed files had the fantastic feature of "Key of reference". 
> > Once you performed a keyed hit via a key, it established a "key of 
> > reference." (not every 
> > x86-wanna-be-a-real-computer-one-day-when-I-grow-up platforms have 
> > any concept like this) Once you did a keyed hit for the 10 record, 
> > you could sequentially process the order/invoice/whatever until the 
> > primary number changed. The record types put everything in the proper 
> > order for printing, screen display, general processing, etc.
> In SQL you just put in the ORDER BY's you need. Maybe not as 
> efficient (that all depends on the databases query optimizer). 
> But it is very simple to use. 

See above.



More information about the Info-vax mailing list