Conference iosg::all-in-1_v30

    I ran the IVP again off the menu - and it shows the account
    creation test failing.
    
    But that first message was kind of strange.
    
    Sondra
    

    I did a set host/log and the message in the original note was the
    message in that log file.  The ALLIN1_ivp.log and the log files in
    OA$IVP_ENGLISH: did not contain anything.
    
    But I got past that and on to another problem.  When running IVP from
    ALLIN1/user=ivp it shows the account creation failing.  When I run it,
    the IVP procedure fails on the form "Create a New Account".  In
    response to "When deleting the VMS account, delete from directory:  it
    show IVP but comes back with the message "Invalid Direcory".  I'm not
    sure what to put in here to get past this point.  I tried the device
    and directory on the lines above this question, but it doesn't like
    that either.
    
    Does any of this make sense.
    
    Any help would be appreciated.
    
    Thanks,
    

    OK the IAC IVP has been known to fail if the OA$IVP_BATCH queue
    exists from a previous run, but as you did a fresh install that
    sounds a little unlikely but anyway....
    
    .... try deleting the IVP_BATCH queue and rerunning the IVP.
    
    There are about 15 (a guess) other STARS articles on v3 IVP failures
    and I really don't have time to list them all here so i'll go with
    that guess and see whether it works.
    
    regards,
    
    Andrew.D.Wicks
    
    

    Before this message I did get a message regarding failure to to the
    batch que problem, but I will try it one more time for good measure. 
    In the meantime any other ideas would be appreciated.
    
    Sondra

    I gave it one more try.  It still fails with invalid directory.
    
    What are these other IVP failures.
    
    Thanks

    
    
    Did any of the IVPs after IAC run ?
    
    This would explain the lack of a log during installation time as
    the IVPs will get a little tied up if IAC runs into problems.
    
    It would seem that something is being unrecognised in the forms which
    create/delete the account. Perhaps the account template is wrong
    somehow.
    
    Sorry I can't help more, I'll make sure our installation expert get
    onto this one.
    
    
    Kevin.
    ~~~~~~
    
    
    

    When running from the menu, the other procedures following IAC show as
    passed.  I also now am seeing the logs.  Previously I had some logs,
    but none which showed failures.  Also the first time I logged into
    ALLIN/USER=IVP it appeared that the tests following IAC had not run
    since the fields for those test results were blank.  Now all show
    passed except IAC.
    
    The current log file for IAC shows the following
    
    %ivp-i-iac,  Running create account check
     "           Creating account
    [MESS]
    {mess]
    [mess] Enter data for new record
    [mess] Invalid Directory - This appear mult times since I tried
           different things
    [mess] Job abandoned at user request
    %ivp-e-iac, Error in SM_SUBMIT_CREATE.SCP Please investigate
    %IVP-i-iac, Create account check has failed
    
    Thanks again for any help
    
    Sondra

    Just for more information - I've been working with this some more and
    have been able to create and delete accounts without any problems.

Hi there,

The unusual symptom of the IAC IVP stalling at the DELETE_FROM field on form 
SM$CREATE$VMS is due to a problem with the validation of this field.  This
problem has already been fixed for a future release.

The IAC IVP uses a template that it creates; the disk name used for this is
determined from PROFIL.DIRECT["IVP"].  If this disk name happens to be a logical
that points to another logical and then to the disk physical name,

e.g.

    "TEST$DISK" = "USER1" (LNM$SYSTEM_TABLE)
  1 "USER1" = "$10$DIA3:" (LNM$SYSTEM_TABLE)

the disk name is accepted by the validation on field UAF_DEV (device) of form
SM$CREATE$VMS, however, the validation of the DELETE_FROM field rejects the disk
name.

I think that this is the problem you are seeing.  To get the IAC IVP to run:-

Run ALL-IN-1 and do <GET PROFIL.DIRECT["IVP"] and you can see the disk logical
name that is being used.

e.g.
	TEST$DISK:[ALLIN1.IVPUSER]

  At VMS show this logical.  Does it point to another logical?  Note the name of
the logical that points directly to the disk phyical name i.e. USER1 in the 
example above.

Using the ALL-IN-1 manager account run ALL-IN-1 and change the IVP users DIRECT
so that the lower logical is used.

<WRITE CHANGE PROFIL USER="IVP", DIRECT = "USER1:[ALLIN1.IVPUSER]"

Now run the IAC IVP, which should work OK now.

Cheers,
	Chris (the so-called installation expert (?)  Thanks Kev!)