Re: Problem with RISC Version on AS/SET

[GaryWWest@xxxxxxx]

In a message dated 8/3/98 7:39:09 PM Central Daylight Time,
ehunkins@centuryinter.net writes:

> GETREC looping with newer versions of Asset
>  
>  I have run into this problem several times. Some where in Asset's history (
> in the
>  v4 era) the generator was changed from
>  making code that just aquires a record, to a multi user method where a 
> record is
>  aquired, then let go, and re-aquired
>  when an update or refresh is needed. I think your problem has more to due 
> with
>  your data than with Asset.
>  Programs wrote in Asset will ALWAYS go into an endless loop if there are 
> records
>  in the file with duplicate data for the
>  key structure being used (logical). I every case in the past where I have 
> run into
>  programs looping on the GETREC intruction,
>  it has always turned out to be the data. I hope that helps.


This would be true if:
1) the file has duplicate keys
2) the data model has the file defined as unique access path
3) you are updating the file



>  
>  MrLennyB@aol.com wrote:
>  
>  > Dear AS/SET users,
>  >
>  > Has anyone run into situations where AS/SET version 4.0.x CICS programs 
> being
>  > recomplied under a RISC version of AS/SET, say version 6.04, act 
> differently.
>  >
>  > We have recompiled several action diagrams and when the programs are 
> executed
>  > they go into a never ending loop when doing a GETREC and not finding a 
> record.
>  >
>  > At this point we are stumped and we need to century date a bolt on 
> application
>  > we wrote in AS/SET for BPCS Version 4.0.4.
>  >
>  > I would appreciate any input or help.  We called SSA HelpLine two weeks 
> ago
>  > and we wait!
>  >
>  > Lenny Bellott
>  > Shop-Vac Corp.
>  > Williamsport, PA
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---