[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

2734.0. "ALLIN1/NOINIT FOR Loop and \\FORCE " by AIMTEC::BUTLER_T () Wed May 19 1993 19:53

    Hello:
    
    
    Any ideas, suggestions, or explanations *greatly* appreciated.  This
    bank is getting ready to ship a product out the door and the outside
    consultant and the managers are cya'ing.  Thus, they would like an
    explanation.
    
    ALL-IN-1 V2.4 and V3.0.
    
    We have a script with a \\force as part of a FOR Function.  When 
    the script is executed interactively it works fine.  If the script
    is run in batch and/or ALL-IN-1/NOINIT - it goes through one time
    up to the \\force.  Removing the \\force, it works fine.
    This can be duplicated with any script.  The example below is from
    the customer call:
    
    $ALLIN1/NOINIT
    OA$INI_INIT
    OA$INI_GLOBALS
    OA$INI_LOGICALS
    MAIL INIT
    DO OA$LIB:MAIL_DIR_CONVERT
    EXIT
    $EXIT
    
    contents of the script:
    
    
    FOR profil WITH NOT -
    (.user = "@" OR .user <=> ":" OR .user == "MANAGER"    OR .user ==
    "IVP" -
                                  OR .user == "POSTMASTER" OR .user ==
    "BOOT" ) -
     DO WRITE CHANGE profil user = .user, mdflag = OA$Y
    
    FOR profil WITH (.mdflag EQS OA$Y AND .user NES "MANAGER") DO -
                    GET #dds_account = .user\\ -
                    GET OA$DISPLAY = OA$_EMDDSADDSUB .user\\FORCE\\ -
                    DO SUBSCRIBER_ADD
    
    GET OA$DISPLAY OA$_GBL_OPERATION_SUCCESSFUL\FORCE
         
    
    Again, it has nothing to do with this script, it has been duplicated.
    
    Thanks,
    
    Tim
T.RTitleUserPersonal
Name		DateLines
2734.2Possible workroundsIOSG::MAURICENight rolls in, my dark companionThu May 20 1993 10:0415
    Yes this is a known problem with the FORCE function, that is fixed in
    the PFR. FORCE returns an error in batch mode, so you may need some
    trickery to work-round it. You could try:
    
    a) get oa$function = "force"
    
    b) .fx force
    
    c) do script which contains a 1 line force function
    
    Hopefully one of these will work.
    
    HTH
    
    Stuart
2734.4OK, but...SWAM2::RHODEWALT_BRPillage pillage, loot lootThu May 20 1993 14:406
    Well, what was the fix? 
    
    Please let the rest of us know. I can easily imagine encountering this
    problem myself some day.
    
    Bruce
2734.5Pick One and Try It!AIMTEC::BUTLER_TThu May 20 1993 16:278
    Bruce,
    
    The customer just wanted an explanation - the workaround was to
    take out the \\force.
    
    I will try the others as soon as possible.
    
    Tim
2734.6Re .4: I expect it was a code fix!IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeThu May 20 1993 18:120
2734.7Just Checking !AIMTEC::BUTLER_TThu May 20 1993 18:492
    Should I be glad I missed the .1 and .3 replies?  I guess
    I'll go talk to my moderator in the cell accross from me.
2734.8Moderation!IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeThu May 20 1993 18:596
    The .1 was my first guess, superseded by Stuart's definitive statement.
    The .3 was a thanks which I delete after they've been seen.
    
    And this (and .-1 :-) ) will disappear too!
    
    Graham