[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

2658.0. "CTERM protocol as opposed to LAT FCS does not work" by TINNIE::SETHI (Ah (-: an upside down smile from Oz) Wed May 05 1993 04:17

    G'day ALL-IN-1'ers and FCServers people :-),
    
    ALL-IN-1 IOS 3.0 is installed at the site.
    
    A customer has a problem accessing shared drawers in that whne they try
    to access it an error message is displayed "No such drawer".  The
    problem only occurs for users who are using the CTERM protocol to
    connect to the VAX as opposed to LAT.
    
    In other words doing a set host/lat is fine but doing a set host/cterm
    causes a problem.  Please note that "/cterm" is used on the PC's and
    how it works is if you do sethost it tries to connect using lat if it
    cannot providing you have cterm loaded it will use cterm.
    
    Is CTERM protocol supported ?  I have a feeling it may not be so I
    would be grateful for your input.
    
    Regards,
    
    Sunil
T.RTitleUserPersonal
Name		DateLines
2658.1do you get the CLD rAIMTEC::WICKS_Aon the Streets of San FranciscoWed May 05 1993 04:297
    Sunil,
    
    there's a CLD (CXO10180) open on something like this.
    
    Regards,
    
    andrew.d.wicks
2658.2Sorry it's not the same problem boyo :-)TINNIE::SETHIAh (-: an upside down smile from OzWed May 05 1993 06:3319
    Hi Andrew,
    
    >-< do you get the CLD r >-
    
    Well Hong get's them so I could get access to them.  I have seen the
    CLD and it's for another problem with set host and entering ALL-IN-1
    "/hardcopy".
    
    This problem is to do with the way DECnet, FCS and Objects in the NCP
    database interact.  Using CTERM as the protocol may cause some problems
    in this interaction that's my guess.  It maybe an ommission or a 
    misfeature/bug.
    
    By the way I got my stand in secretary I ment my manager to look up
    this CLD :-).  Well it's about time we gave them some work to do :-).
    
    Regards,
    
    Sunil
2658.3Shouldn't matterCHRLIE::HUSTONWed May 05 1993 15:0411
    
    Not having seen the CLD that Andrew mentions. I would say that no
    there should be no problem using CTERM, the FCS doesn't care.
    
    You are logged into VMS, then that's all the FCS cares about, it
    doesn't care how you got there. 
    
    Can you get an FCS trace of the error?
    
    --Bob
2658.4Sounds like a quota problem...IOSG::CHINNICKgone walkaboutFri May 14 1993 12:5317
    As advice from the specialist who solved CXO10180...
    
    Check the following (in decreasing order of significance/likelyhood):
    
    	- BYTLM for the user account is sufficient - try increasing it.
    		(suggest minimum 30k bytes) (AUTHORIZE)
    	- MAXBUF for the system is min 8192 (SYSGEN)
    	- you have sufficient non-paged and paged pool (SHOW MEM/POOL)
    
    CXO10180 was a hardcopy problem because of MAXBUF being too low. LAT
    and ordinary terminal buffered I/O uses a different header on I/O
    buffers to CTERM. Because CTERM added extra overhead it hit the MAXBUF
    limitation. [This is the best guess anyway - I haven't checked the VMS
    source code to confirm this.]
    
    Your problem sounds like it could be related but it most likely to be
    BYTLM. [Network mailboxes and I/O use buffered I/O.]
2658.5A solution but needs improving on. Any ideas how too ?BUSHIE::SETHIAhhhh (-: an upside down smile from OZThu May 27 1993 03:5818
    Hi All,
    
    Finally this problem has been solved !!  What happens with a CTERM
    connection is that it's using NETWORK login access and the file cabinets
    need to give access to WORLD: this is what the customer did, when they
    discovered what was causing the problem.
    
    Now I don't think this is a good solution setting the protection to
    w:rwed BUT the customer does not want to change the protection.  Along
    the lines of it works now so don't touch it !!!
    
    So is there a better way you could use ACL's on the file cabinet what
    do I use as the identifier in this case ?  The login via CTERM is not
    classed as an interactive login that's why there was a problem.
    
    Regards,
    
    Sunil