[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

4112.0. "COMMAND function doesn't work!" by GIDDAY::JOYCE (Burn me kangaroo down sport) Wed Apr 27 1994 09:50

    Folks,
    
    ALL-IN-1 V2.4 PAT option (yuk)
    
    A customer is having trouble with this (surprise surprise).  It is
    failing to "prepare file cabinet" and closer investigation shows that,
    although the shared messages are getting "archived" okay they are not
    being backed up into a saveset.
    
    I was able to recover the user and tried the PAT again after sticking 
    tracing and DCL verify on (by putting an OA$TRA_SET LOG,ALL and GET
    OA$DCL="SET VERIFY" commands in MANAGER's OAINI.SCP so they get picked up 
    by the batch job)
    
    The tracing shows that the com file OA$LIB:SM_PAT_SWITCH_SAVESET is not
    being executed!  Sure, the trace says...
    
    	COMMAND OA$LIB:SM_PAT_SWITCH_SAVESET
    
    but it doesn't actually do it!  I've stuck a bucket-full of "SHOW SYM",
    "WRITE SYS$OUTPUT" and "SET VERIFY" commands in the command procedure
    but there is no evidence that it runs at all - and the status symbol it
    sets to 0 or 1 is still null afterwards.
    
    The command file is owned by ALLIN1 and the prot-mask is (RWE,RWE,,). 
    The PAT is being done by the MANAGER account.  I can run the command
    procedure manually from the MANAGER account (but of course it doesn't
    work properly out of context).
    
    Any ideas why this command procedure won't run???
    
    Andy
    CSC Sydney
T.RTitleUserPersonal
Name		DateLines
4112.1A1SUB.lOG ?UTRTSC::SMEETSAlpha AXP Compatible LinkWorks MouseWed Apr 27 1994 12:0910
Hello Andy,


Did you look in the file a1sub.log ? There you should be able to find your
output from Write SYS$OUTPUT and SHOW symbol.


Just a thought,

Martin
4112.2V2.4 OAFC$PART_SEED.EXE is brokeGIDDAY::JOYCEBurn me kangaroo down sportThu Apr 28 1994 11:1638
    Re .-1
    Spot on! I forgot to look in A1SUB.LOg and when I did it gave me a BIG
    clue...
    
    The basic problem was this;
    
    The MUA_PAT.COM procedure has been modified (presumably by the TCP-
    this is V2.4 remember?) to run the script OA$LIB:SM_ADD_PARTITION.SCP
    which in turn runs the image OA$LIB:OAFC$PART_SEED in the sub-process.
    
    Now, this image presents a menu and the script feeds it the "commands"
    to select the option to add a partition entry for a specific user, the
    username and finally the option to exit the menu and return to DCL.
    
    The problem is that the exit option doesn't work so the menu is not
    exited - so subsequent DCL commands intended to be run in the
    sub-process (such as COMMAND OA$LIB:SM_PAT_SWITCH_SAVESET.COM) just get
    fed to the menu system which spits 'em out!
    
    The ONLY way I could get the menu to exit when I ran it interactively
    was to CTRL-C it so I added an OA$SUB_CLOSE to MUA_PAT.COM after the
    "DO OA$LIB:SM_ADD_PARTITION" function.  This blows away the sub-process
    so that the next DCL command gets a nice new squaky-clean one to work
    in.
    
    The PAT now works and the customer is happy.
    
    What still troubles me tho is;
    
    1)	WHY add a partition record for an account that is just about to be
    moved off this system?
    
    2)	WHY doesn't OA$LIB:OAFC$PART_SEED.EXE work properly?
    
    I KNOW these are V2.4 issues but we still support V2.4 (don't we?)...
    
    Andy
    CSC Sydney