[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

1158.0. "INPSTRTRU creating a new USER ..." by TAV02::CHAIM (Semper ubi Sub ubi .....) Sun Aug 02 1992 14:25

A customer has described the following strange problem since upgrading from
ALL-IN-1 V2.3 to ALL-IN-1 V2.4:

He is NOT able to create a user account. The log file shows the following error
during execution of oa$lib:mua_create

$ if $status then go
%lib-f-inpstrtru, Input String Truncated

The line is actually
$ if $status then goto inc_retry_count

I asked the customer to comment out the line, and then he gets the following
(notice that the o of go is truncated - since the ! was added):

$! if $status then g
%lib-f-inpstrtru, Input String Truncated
 
I have a feeling this is basically a VMS/DCL problem, but I'll give it a shot
here first.

Thanks,

Cb.
T.RTitleUserPersonal
Name
DateLines
1158.1DIR/FULLIOSG::TALLETTArranging bits for a living...Mon Aug 03 1992 12:479
    	Wild guess:
    
    	Does the customer use a "funny" editor? Do a DIR/FULL on
    	MUA_CREATE.COM, it soiunds like the attributes are wrong and
    	someone is ignoring the line breaks and trying to read in the
    	whole file.
    
    Regards,
    Paul
1158.2MUA_CREATE.COM file is impeccable..TAV02::CHAIMSemper ubi Sub ubi .....Mon Aug 03 1992 14:4129
Paul,
Paul,

When I saw the log file and the truncated line, that is the first thing I
thought of. However, the file itself is impeccable (did ana/rms as well to make
sure - copied it - you name it). Also, the moment we added the ! to the line,
the truncation was one character less.

In the meantime, we checked the UAF quotas for the ALLIN1 account, and they
appear to be sufficient (they were >= those for the ALLIN1 account on our
system). Also checked PIOPAGES and CTLPAGES, and both of these seem to be
sufficient.

Now he's checking to see if this is the only procedure causing any sort of
problem or are other batch jobs also causing problems.


>        Wild guess:
>    
>        Does the customer use a "funny" editor? Do a DIR/FULL on
>        MUA_CREATE.COM, it soiunds like the attributes are wrong and
>        someone is ignoring the line breaks and trying to read in the
>        whole file.

Keep those ideas comin...

Thanks,

Cb.
1158.3Get a new fileWAYLND::HOWARDOur business is computers not moneyThu Aug 06 1992 19:1812
    Could there be an error on the line before the one that has the
    problem?  You might also try getting a new copy of the file off the
    saveset.  Theoretically, all the corruption should have been cleared up
    by what you did, but I have seen errors which defied attempts to
    correct them. You might even try deleting the line and retyping it. 
    Editors sometimes ignore characters they don't like in the display, but
    write them out just fine.  Also, since this is apparently being
    executed by the COMMAND function, it is conceivable that there is a
    logical name conflict or something making ALL-IN-1 overflow some buffer
    it uses to talk to DCL in the sub-process.
    
    Ben
1158.4More input ...TAV02::CHAIMSemper ubi Sub ubi .....Mon Aug 10 1992 10:1534
Re .3:

The mua_create is running as a batch job and not in the A1 subprocess via
COMMAND. Thus I doubt it has anything to do with the mailbox.

I have yet to solve this problem, but I made an on-site visit, and I do have
some new input.

It appears now that the line within mua_create which is causing the problem is
definitely:

$	UAF SHOW 'vms_uic'
$	if $status then goto ...

1. If I totally comment out both lines, then the procedure does successfully
complete - of course the check on the UIC is not done.

2. If I add several comment lines 
 
$	UAF SHOW 'vms_uic'
$!
$!
$	if $status then goto ...

then the error returned is not INPSTRTRU but rather %RMS-F-EOF.

This one really has me baffled. As mentioned before, I've cross posted this
problem to VMSNOTES, but as of yet noone there has come up with anything
concrete.

Thanks,

Cb.