[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

222.0. "dropping field after decimal place" by KAORSC::M_FETT () Thu Mar 12 1992 18:58

    
    Customer is running V2.4, has designed a set of forms.
    The first form is to be filled in with numbers in certain 
    fields by the user, the second form contains a few pre-processed
    fields (calculated by the input of the fields in the first form).
    
    When the user is low on account resources (i.e. they have been
    in ALL-IN-1 a while) the final amount on the preprocessed field
    will come out to a whole number (i.e. 3.0). However, if that user logs out
    and logs back into ALL-IN-1 and checks that pre-processed field
    again, it will have the correct value (i.e. 3.2).
    
    So somehow the user's result field drops the value after the decimal
    place if the account is low on resources. (The customer said that
    usually bumping up Working Set will workaround this problem).
    
    Has anyone heard of this problem?
    
    Monica
T.RTitleUserPersonal
Name		DateLines
222.1More info please.UTRTSC::BOSMANWe're just sugar mice in the rainFri Mar 13 1992 09:396
    Monica,
    
    Sounds like black magic to me (but one never knows with ALL-IN-1).
    Please give us some more details about the code ...
    
    Sjaak.
222.2That ol black magic scriptKAORSC::M_FETTThu Mar 19 1992 18:2498
    I've managed to get him to give me some more info; here's the
    script; although I can't see anything that would hog up the user's
    resources, or screw up if the resources are low:
    

The contents of the script that does the evaluation:


!+
!       PA_EVALUTATION_DO.SCP
!
!       This script is only invoked when we touch the field
!       PA_PART_II_R2, it does some computation for the employee's
!       overall employment evaluation.
!
!       This is done when we go from form 7 (7 of 9) to form 8 (8 or 9)
! 
!       If the question rating is 0 this means that the question is
!       N/A to that employee and should not be entered in the 
!       calculation.
!
!+
.LABEL START
get #pa_part_ii_r1 = 0
get #pa_part_ii_r2 = 0
get #pa_part_ii_r3 = 0
get #pa_part_ii_r4 = 0
!
.if pa_part_i_1r eq 0 then .goto next_2
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_1r
!
.label next_2
.if pa_part_i_2r eq 0 then .goto next_3
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_2r
!
.label next_3
.if pa_part_i_3r eq 0 then .goto next_4
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_3r
!
.label next_4
.if pa_part_i_4r eq 0 then .goto next_5
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_4r
!
.label next_5
.if pa_part_i_5r eq 0 then .goto next_6
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_5r
!
.label next_6
.if pa_part_i_6r eq 0 then .goto next_7
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_6r
!
.label next_7
.if pa_part_i_7r eq 0 then .goto next_8
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_7r
!
.label next_8
.if pa_part_i_8r eq 0 then .goto next_9
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_8r
!
.label next_9
.if pa_part_i_9r eq 0 then .goto next_10
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_9r
!
.label next_10
.if pa_part_i_10r eq 0 then .goto next_11
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_10r
!
.label next_11
.if pa_part_i_11r eq 0 then .goto next_12
 compute #pa_part_ii_2_r2 = #pa_part_ii_2_r2 + 1
 compute #pa_part_ii_2_r1 = #pa_part_ii_2_r1 + pa_part_i_11r
!
.label next_12
.if pa_part_ii_rl eq 0 then .goto label_exit
 compute #pa_part_ii_2_r3 = #pa_part_ii_2_r1 + #pa_part_ii_2_r2
!
.if #pa_part_ii_2_r3 ge "4.6" then get #pa_part_ii_2_r4 = 5
.if #pa_part_ii_2_r3 ge "4.5" then get #pa_part_ii_2_r4 = 4
.if #pa_part_ii_2_r3 ge "3.5" then get #pa_part_ii_2_r4 = 3
.if #pa_part_ii_2_r3 ge "2.5" then get #pa_part_ii_2_r4 = 2
.if #pa_part_ii_2_r3 ge "1.5" then get #pa_part_ii_2_r4 = 1
.LABEL LABEL_EXIT
.EXIT
    
    
    
        - Monica
222.3SorryUTRTSC::BOSMANWe're just sugar mice in the rainTue Mar 24 1992 07:224
    I can't see anything that causes your problem, sorry. Useally I would
    like to see it if such problems occur, and then use trace to trace it.
    
    Succes, Sjaak.
222.4Hard to recreateKAORSC::M_FETTTue Mar 24 1992 15:568
    Customer claims that he himself is having a hard time recreating
    this problem, because it only seems to occur for people who have 
    been spending a long time doing various activities within ALL-IN-1
    before they ever start using his application. In that case a 
    trace would be *MILES* long......
    
    
    Monica
222.5Why?UTRTSC::BOSMANWe're just sugar mice in the rainWed Mar 25 1992 09:004
    The trace doesn't have to be that long; don't activate trace until the
    problem occurs. I assume that, once the problem occurs, it will remain.
    
    Sjaak.
222.6Check the code again... Missing DECIMAL 1SHALOT::WARFORDRichard Warford @OPA DTN 393-7495Sun Mar 29 1992 16:145
    Sounds more likely that somewhere along the line they execute a 
    DECIMAL I function. And I would guess the preprocessing doesn't
    reset it back to a DECIMAL 1 or /DECIMAL=1.
    
    Rick