[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

2612.0. "QUO_ILL_CMDLINE and CMATNDWRITERR ???" by VNABRW::EHRLICH_K (The Pit and the Pendulum!) Mon Apr 26 1993 12:59

Hi all,

	one of my customer has detected two errormessages which I
can't find in any form or in any script. Only in OA.a1$msg I find
    the symbol containing the reason. We're using ALL-IN-1 V3.0-1 German
    with VMS V5.5-2.

The first is:

QUO_ILL_CMDLINE <Sie haben einen oder mehrere unzul�ssige Parameter angegeben.>
	
and appears on the screen when one user is trying to edit a SharedDrawer (Typ=
regular shared.) 

I'll think that this errormessage comes from the CHECK_DISKQUOTA function.
	
The last is:

CMATNDWRITERR   <Fehler beim Ausf�llen der Teilnehmerliste.>

and happens when an user sends an reply to a meeting to the invitor. When the
invitor is going to read the new mail this errormessage appears on the screen
and the mailmessage stays in the INBOX status UNREAD.????

Here I really don't know where the problem can lie. Where/What can I check ...

Many thanks for all your inputs in advance

Best regards

Charly_from_CSC_Vienna
T.RTitleUserPersonal
Name		DateLines
2612.1post installationproblemAIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Mon Apr 26 1993 14:075
        The second problem is cause by the MEETING.DAT file failing to be
        converted during the upgrade.  The new file should be fixed length
        748 byte records.  The cause is usually a customized MEETING.FDL.
        
        Dave Zaniewski
2612.2Well, QUO_ILL_CMDLINE can mean.....IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeMon Apr 26 1993 16:5614
    QUO_ILL_CMDLINE is only used from BLISS modules according to my cross
    reference.
    
    It is signalled if the device name or volume name aren't found, or
    aren't discs according to $GETDVI. It can also come out if we fail to
    get the user's UIC with $GETJPI, or from the UAF. Or if the account
    doesn't exist. It's also a catch all error from the various system
    services that try and access the disc. Also if the specified values for
    the threshold for the quota check isn't numeric, or if the symbols
    specified for the answers from the call are invalid.
    
    There, that should narrow down your search for the problem a bit :-)
    
    Graham
2612.3I'm going on shooting (the trouble)...VNABRW::EHRLICH_KThe Pit and the Pendulum!Mon Apr 26 1993 17:099
    Dave, Graham,
    
    	thanks a lot for this information, so now I'm going on with 
    troubleshooting at customers' site.
    
    I'll keep you informed here.
    
    Best regards
    Charly_from_CSC_Vienna
2612.4Just an update, all's fixed!VNABRW::EHRLICH_KThe Pit and the Pendulum!Fri May 14 1993 16:3914
    Dear Dave and Graham,
    
    	the first problem was a result of having a slash - yeah, really
    a '/' - in an accountname like and therefore in the MAINdrawer.
    
    The solution for the second problem was due to a corrupt ATTENDEE.DAT
    file.
    
    I've done all recommended things described in the STARS article, called
    'V2.4 to V3.0 Upgrade Potential Time Management Problems and
    Resoultions' and it works now fine.
    
    Regards, and thanks again
    Charly