| Title: | X.500 Directory Services |
| Notice: | Sprt: FORTY2::X500_SUPPORT, Kits: 216.*, try dir/titl=OFFICIAL |
| Moderator: | FORTY2::PULLEN |
| Created: | Tue Jan 30 1990 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1016 |
| Total number of notes: | 4299 |
ALPHA running OPEN VMS 7.1
X500 3.0
We know this configuration is not officially supported. However,
the customer said he was told at DECUS, last week, that the
X500 Directory, along with MAILbus 400 should work on a VMS 7.1 system.
This is a test system and he can restore his VMS 6.2 system if required.
When we tried to enable the DSA, it stated resource unavailable.
We tried stopping the DSA and rerunning the startup script.
During the startup the DXD$DSA_SERVER process is created, and
as soon as the process is created, he gets an error resource
unavailable. We even tried to reboot the system, which gave us
the same results.
The DSA state says off no matter what we try. The template is
present and we can show the DSA NAMING CONTEXT successfully.
Do you have any suggestions on what we could try? Would upgrading
to X500 3.1 help?
Thanks in advance.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1012.1 | FORTY2::PULLEN | Julian Pullen | Thu May 29 1997 13:38 | 12 | |
X.500 V3.0 and V3.1 have not been certified against
VMS V7.1, but we dont known of any reason why they
should not work. We will be certifying X.500 V3.1
on VMS V7.1 shortly.
I have already come across a similarly "enable" error on
a VMS V7.1 system which turned out to be an OSAK problem. I found
the problem when I tried stop and re-start OSAK. OSAK would
not start cleanly.
Julian
| |||||
| 1012.2 | IP$16.65.80.19::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Thu May 29 1997 18:05 | 17 | |
> I have already come across a similarly "enable" error on > a VMS V7.1 system which turned out to be an OSAK problem. Can you be more specific? Are you perhaps refering to the OSAK/CMA library problem? re .0; if Julian is correct, then check to make sure that OSAK$NETMAN is running (and for that matter OSAK$SERVER_V3). If not, then that would certainly impact X.500; I would start by examining the accountng.dat file to see what kind of exit status the OSAK processes terminated with. if it was a file-not-found type of error, then edit SYS$STARTUP:OSAK$NETMAN.COM and comment out the DEFINE commands for the CMA$ logicals; then try restarting OSAK. Other than the CMA logical problem, we're not aware of any problems on 7.1 that would prevent OSAK from starting, and OSAK *is* supported on 7.1. --Scott | |||||
| 1012.3 | OSAK version 3.0-L | CX3PST::HTKING::M_SHELDON | Thu May 29 1997 22:02 | 14 | |
Don't know yet whether this is the cause...... but a $product show product on his system shows OSAK V3.0-L On my OpenVMS V7.1 Alpha is shows OSAK V3.0-P It appears the OpenVMS upgrade may not have included OSAK. Customer is upgrading now. Mike Sheldon CSC/CS Network Support | |||||