AFAIK, ACMELDAP and LOGIN got created to exclude the 2 streams of different
code (with different fixes) for logging in (normal vs LDAP) from UPDATE ECOs.

Now with the VMS83A_UPDATE V11, the VMS83A_LOGIN got included again
(while the new VMS831H1I_UPDATE V7 does not include the VMS831H1_LOGIn ECO).

Was this intentional - or is this perhaps (one of) the (possible) reason(s),
why VMS83A_UPDATE V11 got On-Hold again?

btw: When will these 2 streams of (login/SSO) code integrate again? With V8.4?

Anyone any insight?

Many TIA

-EPLAN

PS: ACMELDAP delivers a new V83A_ACMELDAP_STD, V83A_ACMELOGIN kit.
(besides the ACME.EXE, ACME_SERVER.EXE, LDAP$SHR.EXE, VMS$VMS_ACHMESHR.EXE
and SETSHOSERVER.EXE, which are - AFAIK - unused by normal login activities)
Does said ACMELDAP ECO really conflict with LOGIN and or UPDATE ECOs
(in contrast to V83A_ACMELDAP_STD, V83A_ACMELOGIN, which do)?
Shouldn't ACMELDAP better be integrated in UPDATE (while V83A_ACMELDAP_STD,
V83A_ACMELOGIN and VMS83A_LOGIN stay outside)?
I find it strange to install or not install a ECO, which only (?) delivers
a .BCK saveset which I need to unpack and install or not install separately...
-- 
Peter "EPLAN" LANGST�GER
Network and OpenVMS system specialist
E-mail  Peter@LANGSTOeGER.at
A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist

On Dec 15, 4:03=A0am, pe...@langstoeger.at (Peter 'EPLAN' LANGSTOeGER)
wrote:
> AFAIK, ACMELDAP and LOGIN got created to exclude the 2 streams of differe=
nt
> code (with different fixes) for logging in (normal vs LDAP) from UPDATE E=
COs.
>
> Now with the VMS83A_UPDATE V11, the VMS83A_LOGIN got included again
> (while the new VMS831H1I_UPDATE V7 does not include the VMS831H1_LOGIn EC=
O).
>
> Was this intentional - or is this perhaps (one of) the (possible) reason(=
s),
> why VMS83A_UPDATE V11 got On-Hold again?
>
> btw: When will these 2 streams of (login/SSO) code integrate again? With =
V8.4?
>
> Anyone any insight?
>
> Many TIA
>
> -EPLAN
>
> PS: ACMELDAP delivers a new V83A_ACMELDAP_STD, V83A_ACMELOGIN kit.
> (besides the ACME.EXE, ACME_SERVER.EXE, LDAP$SHR.EXE, VMS$VMS_ACHMESHR.EX=
E
> and SETSHOSERVER.EXE, which are - AFAIK - unused by normal login activiti=
es)
> Does said ACMELDAP ECO really conflict with LOGIN and or UPDATE ECOs
> (in contrast to V83A_ACMELDAP_STD, V83A_ACMELOGIN, which do)?
> Shouldn't ACMELDAP better be integrated in UPDATE (while V83A_ACMELDAP_ST=
D,
> V83A_ACMELOGIN and VMS83A_LOGIN stay outside)?
> I find it strange to install or not install a ECO, which only (?) deliver=
s
> a .BCK saveset which I need to unpack and install or not install separate=
ly...
> --
> Peter "EPLAN" LANGST=D6GER
> Network and OpenVMS system specialist
> E-mail =A0Pe...@LANGSTOeGER.at
> A-1030 VIENNA =A0AUSTRIA =A0 =A0 =A0 =A0 =A0 =A0 =A0I'm not a pessimist, =
I'm a realist

>>> (while the new VMS831H1I_UPDATE V7 does not include the VMS831H1_LOGIn =
ECO).

That's good to know. I purposely left out those ACME LDAP and LOGIN
ECOs for 831H1.