[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

199.0. "Failed to submit batch job" by BREAKR::MIKKELSON (Kill me. I need the money.) Mon Mar 09 1992 18:13

    
    When I try to create a new a new ALL-IN-1 account, I get an error
    message back telling me "Failed to submit batch job".  Looking through
    a trace log of the procedure, I see that #dcl_status has been set to
    229712.  (Apparently the customer has also had problems submitting
    housekeeping jobs at times as well.)  I suppose I should be able to
    translate this error number to a message somehow, but I couldn't seem to
    get anything useful out of F$MESSAGE (I probably did it wrong).
    
    Could someone clue me in on what ALL-IN-1 is trying to tell me?
    
    - David
T.RTitleUserPersonal
Name		DateLines
199.1Looks like a bad qaulifier or keywordBUFFER::VICKERSWinners take action not keep scoreMon Mar 09 1992 19:5015
    David,

    I bit on the F$message and did:

$ Write Sys$Output F$Message(229712)
%CLI-W-VALREQ, missing qualifier or keyword value - supply all required values

    At first I was thinking that I had made a typo but my current view is
    that 229712 is returned with a missing qualifier or keyword value. 
    This makes me think that one of the qualifiers or keywords provided in
    the submit is faulty.  Could it be that the batch queue specified to be
    used is not valid, for instance?

    Have fun,
    don
199.2#uaf_direct not setBREAKR::MIKKELSONKill me. I need the money.Mon Mar 09 1992 21:1714
    
    It appears that the 6th parameter to the MUA_CREATE procedure is
    coming up without a value, causing the error message mentioned
    previously.
    
    This parameter is supposed to contain the value stored in the symbol 
    #uaf_direct, but that symbol has nothing stored in it.  The script
    SA_CREATE_SUBMIT contains a line to set the value of #uaf_direct to 0, but
    SM_SUBMIT_CREATE does not appear to set the value of this symbol at
    all.  Am I missing something from my script, or is this symbol supposed
    to be set elsewhere?
    
    - David
199.3Can I see the log?IOSG::TYLDESLEYThu Mar 12 1992 10:3512
    David,
    
    I know we had to fix a problem around the setting of #uaf_direct
    during the development of V3.0. Can you tell me what baselevel 
    you are on? have you any old forms or scripts lying around in site
    areas? 
    
    For account creations from MGT MUA C CU, the symbol #uaf_direct is
    set up on form SM$CREATE.
    
    Cheers,
    DaveT
199.4BREAKR::MIKKELSONKill me. I need the money.Thu Mar 12 1992 16:599
    
    I found that the problem came about because some of the ALL-IN-1 pieces
    used in creating/deleting/renaming accounts had been customized under
    2.3, and those customized pieces were left around to override the
    newer 2.4 versions.  Once I removed the older versions and updated the
    2.4 versions to incorporate the changes, things worked fine.
    
    - David