D3 and mvBase

I'm in the process of setting up a "golden master"[*] in order to migrate six D3 v9.0 Linux hosts to v10.3.4.

I wanted to get the base D3 install completed before turning the VM over to my infrastructure team for duplication.

I'm installing on RHEL 9 (9.4 specifically) and noticed that nothing has been done regarding systemd during the install process, even though there's some passing acknowledgement in the docs that xinetd is deprecated.  Nothing for telnet, nothing for MVSP.

I didn't know what to do regarding the missing systemd service scripts for telnet, (the word "systemd" doesn't even occur in the 10.3.4 installation guide.  That's problematic.), I figured I'd at least see if I could get MVSP set up - maybe that creates the systemd services.

I'm greeted with this:

:to mvsp

< Connect time= 0 Mins.; CPU= 0 Units; LPTR pages= 0        >
WHICH TCP/IP PORT NUMBER TO USE (9000) ?
DO YOU WANT AN SSL CONNECTION (Y/[N]) ?
Updating configuration. This could take upto 2 minutes to complete, please wait
INSTALL ERROR. CODE = 13
:

I'm going to assume that "13" means, "system not activated"?  If so, why doesn't it just say that?  If not, what on earth does "13" mean?

I should also point out that the MVSP v1.8.20 patch is among the D3 10.3.4 files, instead of with the other MVSP files but has no instructions regarding how the patch is applied.

The instructions for the ABS patch (at least a19) lists the wrong filename for the patch file.  The instructions call out linux1031a19, but the filename for the actual patch is lx64.10.3.x.a19.

So do I need to activate the system in order to configure MVSP and get it to spit out systemd service scripts?  (what about for telnet?  what generates that?)

Thanks folks!

g.

* by "golden master", I mean a fully configured RHEL 9 installation with D3 v10.3.4 installed, but not activated.

you are using a root level user ?
are you loged in d3 using
d3 -b -l 

?

I'm in the process of setting up a "golden master"[*] in order to migrate six D3 v9.0 Linux hosts to v10.3.4.

I wanted to get the base D3 install completed before turning the VM over to my infrastructure team for duplication.

I'm installing on RHEL 9 (9.4 specifically) and noticed that nothing has been done regarding systemd during the install process, even though there's some passing acknowledgement in the docs that xinetd is deprecated.  Nothing for telnet, nothing for MVSP.

I didn't know what to do regarding the missing systemd service scripts for telnet, (the word "systemd" doesn't even occur in the 10.3.4 installation guide.  That's problematic.), I figured I'd at least see if I could get MVSP set up - maybe that creates the systemd services.

I'm greeted with this:

:to mvsp

< Connect time= 0 Mins.; CPU= 0 Units; LPTR pages= 0        >
WHICH TCP/IP PORT NUMBER TO USE (9000) ?
DO YOU WANT AN SSL CONNECTION (Y/[N]) ?
Updating configuration. This could take upto 2 minutes to complete, please wait
INSTALL ERROR. CODE = 13
:

I'm going to assume that "13" means, "system not activated"?  If so, why doesn't it just say that?  If not, what on earth does "13" mean?

I should also point out that the MVSP v1.8.20 patch is among the D3 10.3.4 files, instead of with the other MVSP files but has no instructions regarding how the patch is applied.

The instructions for the ABS patch (at least a19) lists the wrong filename for the patch file.  The instructions call out linux1031a19, but the filename for the actual patch is lx64.10.3.x.a19.

So do I need to activate the system in order to configure MVSP and get it to spit out systemd service scripts?  (what about for telnet?  what generates that?)

Thanks folks!

g.

* by "golden master", I mean a fully configured RHEL 9 installation with D3 v10.3.4 installed, but not activated.

I wasn't using the -b, so tried that.  Same error.

Thanks.

g.

you are using a root level user ?
are you loged in d3 using
d3 -b -l 

?

I'm in the process of setting up a "golden master"[*] in order to migrate six D3 v9.0 Linux hosts to v10.3.4.

I wanted to get the base D3 install completed before turning the VM over to my infrastructure team for duplication.

I'm installing on RHEL 9 (9.4 specifically) and noticed that nothing has been done regarding systemd during the install process, even though there's some passing acknowledgement in the docs that xinetd is deprecated.  Nothing for telnet, nothing for MVSP.

I didn't know what to do regarding the missing systemd service scripts for telnet, (the word "systemd" doesn't even occur in the 10.3.4 installation guide.  That's problematic.), I figured I'd at least see if I could get MVSP set up - maybe that creates the systemd services.

I'm greeted with this:

:to mvsp

< Connect time= 0 Mins.; CPU= 0 Units; LPTR pages= 0        >
WHICH TCP/IP PORT NUMBER TO USE (9000) ?
DO YOU WANT AN SSL CONNECTION (Y/[N]) ?
Updating configuration. This could take upto 2 minutes to complete, please wait
INSTALL ERROR. CODE = 13
:

I'm going to assume that "13" means, "system not activated"?  If so, why doesn't it just say that?  If not, what on earth does "13" mean?

I should also point out that the MVSP v1.8.20 patch is among the D3 10.3.4 files, instead of with the other MVSP files but has no instructions regarding how the patch is applied.

The instructions for the ABS patch (at least a19) lists the wrong filename for the patch file.  The instructions call out linux1031a19, but the filename for the actual patch is lx64.10.3.x.a19.

So do I need to activate the system in order to configure MVSP and get it to spit out systemd service scripts?  (what about for telnet?  what generates that?)

Thanks folks!

g.

* by "golden master", I mean a fully configured RHEL 9 installation with D3 v10.3.4 installed, but not activated.

Were you doing this as root ?

MVSP setup does create a system service to handle MVSP connections.

I wasn't using the -b, so tried that.  Same error.

Thanks.

g.

you are using a root level user ?
are you loged in d3 using
d3 -b -l 

?

I'm in the process of setting up a "golden master"[*] in order to migrate six D3 v9.0 Linux hosts to v10.3.4.

I wanted to get the base D3 install completed before turning the VM over to my infrastructure team for duplication.

I'm installing on RHEL 9 (9.4 specifically) and noticed that nothing has been done regarding systemd during the install process, even though there's some passing acknowledgement in the docs that xinetd is deprecated.  Nothing for telnet, nothing for MVSP.

I didn't know what to do regarding the missing systemd service scripts for telnet, (the word "systemd" doesn't even occur in the 10.3.4 installation guide.  That's problematic.), I figured I'd at least see if I could get MVSP set up - maybe that creates the systemd services.

I'm greeted with this:

:to mvsp

< Connect time= 0 Mins.; CPU= 0 Units; LPTR pages= 0        >
WHICH TCP/IP PORT NUMBER TO USE (9000) ?
DO YOU WANT AN SSL CONNECTION (Y/[N]) ?
Updating configuration. This could take upto 2 minutes to complete, please wait
INSTALL ERROR. CODE = 13
:

I'm going to assume that "13" means, "system not activated"?  If so, why doesn't it just say that?  If not, what on earth does "13" mean?

I should also point out that the MVSP v1.8.20 patch is among the D3 10.3.4 files, instead of with the other MVSP files but has no instructions regarding how the patch is applied.

The instructions for the ABS patch (at least a19) lists the wrong filename for the patch file.  The instructions call out linux1031a19, but the filename for the actual patch is lx64.10.3.x.a19.

So do I need to activate the system in order to configure MVSP and get it to spit out systemd service scripts?  (what about for telnet?  what generates that?)

Thanks folks!

g.

* by "golden master", I mean a fully configured RHEL 9 installation with D3 v10.3.4 installed, but not activated.

I'm in the process of setting up a "golden master"[*] in order to migrate six D3 v9.0 Linux hosts to v10.3.4.

I wanted to get the base D3 install completed before turning the VM over to my infrastructure team for duplication.

I'm installing on RHEL 9 (9.4 specifically) and noticed that nothing has been done regarding systemd during the install process, even though there's some passing acknowledgement in the docs that xinetd is deprecated.  Nothing for telnet, nothing for MVSP.

I didn't know what to do regarding the missing systemd service scripts for telnet, (the word "systemd" doesn't even occur in the 10.3.4 installation guide.  That's problematic.), I figured I'd at least see if I could get MVSP set up - maybe that creates the systemd services.

I'm greeted with this:

:to mvsp

< Connect time= 0 Mins.; CPU= 0 Units; LPTR pages= 0        >
WHICH TCP/IP PORT NUMBER TO USE (9000) ?
DO YOU WANT AN SSL CONNECTION (Y/[N]) ?
Updating configuration. This could take upto 2 minutes to complete, please wait
INSTALL ERROR. CODE = 13
:

I'm going to assume that "13" means, "system not activated"?  If so, why doesn't it just say that?  If not, what on earth does "13" mean?

I should also point out that the MVSP v1.8.20 patch is among the D3 10.3.4 files, instead of with the other MVSP files but has no instructions regarding how the patch is applied.

The instructions for the ABS patch (at least a19) lists the wrong filename for the patch file.  The instructions call out linux1031a19, but the filename for the actual patch is lx64.10.3.x.a19.

So do I need to activate the system in order to configure MVSP and get it to spit out systemd service scripts?  (what about for telnet?  what generates that?)

Thanks folks!

g.

* by "golden master", I mean a fully configured RHEL 9 installation with D3 v10.3.4 installed, but not activated.

Hi Gene,

Yes, D3 must be activated in order to configure MVSP.  A non activated system doesn't have the features available to access & update the Linux file system.
  

The MVSP v1.8.20 patch is an ACCOUNT-SAVE of the MVSP control account.  It is required on Redhat/Rocky/Alma Linux v9.x for systemd service control.

To patch your system, connect to D3 using "d3 -l", [the -lower-case-l] option, and from DM perform a "DELETE-ACCOUNT MVSP", followed by an account-restore from the MVSP.1.8.20.D3P device; and then "LOGTO MVSP" to complete the setup.

Please note that this file is a NON-Compressed pseudo tape device, (type=floppy).

Hope that helps.

I'm in the process of setting up a "golden master"[*] in order to migrate six D3 v9.0 Linux hosts to v10.3.4.

I wanted to get the base D3 install completed before turning the VM over to my infrastructure team for duplication.

I'm installing on RHEL 9 (9.4 specifically) and noticed that nothing has been done regarding systemd during the install process, even though there's some passing acknowledgement in the docs that xinetd is deprecated.  Nothing for telnet, nothing for MVSP.

I didn't know what to do regarding the missing systemd service scripts for telnet, (the word "systemd" doesn't even occur in the 10.3.4 installation guide.  That's problematic.), I figured I'd at least see if I could get MVSP set up - maybe that creates the systemd services.

I'm greeted with this:

:to mvsp

< Connect time= 0 Mins.; CPU= 0 Units; LPTR pages= 0        >
WHICH TCP/IP PORT NUMBER TO USE (9000) ?
DO YOU WANT AN SSL CONNECTION (Y/[N]) ?
Updating configuration. This could take upto 2 minutes to complete, please wait
INSTALL ERROR. CODE = 13
:

I'm going to assume that "13" means, "system not activated"?  If so, why doesn't it just say that?  If not, what on earth does "13" mean?

I should also point out that the MVSP v1.8.20 patch is among the D3 10.3.4 files, instead of with the other MVSP files but has no instructions regarding how the patch is applied.

The instructions for the ABS patch (at least a19) lists the wrong filename for the patch file.  The instructions call out linux1031a19, but the filename for the actual patch is lx64.10.3.x.a19.

So do I need to activate the system in order to configure MVSP and get it to spit out systemd service scripts?  (what about for telnet?  what generates that?)

Thanks folks!

g.

* by "golden master", I mean a fully configured RHEL 9 installation with D3 v10.3.4 installed, but not activated.

I'm in the process of setting up a "golden master"[*] in order to migrate six D3 v9.0 Linux hosts to v10.3.4.

I wanted to get the base D3 install completed before turning the VM over to my infrastructure team for duplication.

I'm installing on RHEL 9 (9.4 specifically) and noticed that nothing has been done regarding systemd during the install process, even though there's some passing acknowledgement in the docs that xinetd is deprecated.  Nothing for telnet, nothing for MVSP.

I didn't know what to do regarding the missing systemd service scripts for telnet, (the word "systemd" doesn't even occur in the 10.3.4 installation guide.  That's problematic.), I figured I'd at least see if I could get MVSP set up - maybe that creates the systemd services.

I'm greeted with this:

:to mvsp

< Connect time= 0 Mins.; CPU= 0 Units; LPTR pages= 0        >
WHICH TCP/IP PORT NUMBER TO USE (9000) ?
DO YOU WANT AN SSL CONNECTION (Y/[N]) ?
Updating configuration. This could take upto 2 minutes to complete, please wait
INSTALL ERROR. CODE = 13
:

I'm going to assume that "13" means, "system not activated"?  If so, why doesn't it just say that?  If not, what on earth does "13" mean?

I should also point out that the MVSP v1.8.20 patch is among the D3 10.3.4 files, instead of with the other MVSP files but has no instructions regarding how the patch is applied.

The instructions for the ABS patch (at least a19) lists the wrong filename for the patch file.  The instructions call out linux1031a19, but the filename for the actual patch is lx64.10.3.x.a19.

So do I need to activate the system in order to configure MVSP and get it to spit out systemd service scripts?  (what about for telnet?  what generates that?)

Thanks folks!

g.

* by "golden master", I mean a fully configured RHEL 9 installation with D3 v10.3.4 installed, but not activated.

That 1.8.20 is NOT a patch. It's a full account-save of the MVSP account. There's a 1.8.21 available which I'm attaching hereto. Steps:

Make note of the MVSP-enabled accounts

Delete the MVSP account

RESTORE-ACCOUNTS from the pseudo (on D3 Windows, you would add an (R switch to get it into the FSI, but you're on Linux so not needed)

LOGTO the new MVSP account and go through the setup process if asked

Reenable the accounts that were previously MVSP-enabled

BTW, the Forum wouldn't let me upload a .d3p file, so I renamed MVSP_1.8.21.d3p to MVSP_1.8.21.txt. After you download, you can use it as-is, or rename it (my OCD would make me rename it).

I'm in the process of setting up a "golden master"[*] in order to migrate six D3 v9.0 Linux hosts to v10.3.4.

I wanted to get the base D3 install completed before turning the VM over to my infrastructure team for duplication.

I'm installing on RHEL 9 (9.4 specifically) and noticed that nothing has been done regarding systemd during the install process, even though there's some passing acknowledgement in the docs that xinetd is deprecated.  Nothing for telnet, nothing for MVSP.

I didn't know what to do regarding the missing systemd service scripts for telnet, (the word "systemd" doesn't even occur in the 10.3.4 installation guide.  That's problematic.), I figured I'd at least see if I could get MVSP set up - maybe that creates the systemd services.

I'm greeted with this:

:to mvsp

< Connect time= 0 Mins.; CPU= 0 Units; LPTR pages= 0        >
WHICH TCP/IP PORT NUMBER TO USE (9000) ?
DO YOU WANT AN SSL CONNECTION (Y/[N]) ?
Updating configuration. This could take upto 2 minutes to complete, please wait
INSTALL ERROR. CODE = 13
:

I'm going to assume that "13" means, "system not activated"?  If so, why doesn't it just say that?  If not, what on earth does "13" mean?

I should also point out that the MVSP v1.8.20 patch is among the D3 10.3.4 files, instead of with the other MVSP files but has no instructions regarding how the patch is applied.

The instructions for the ABS patch (at least a19) lists the wrong filename for the patch file.  The instructions call out linux1031a19, but the filename for the actual patch is lx64.10.3.x.a19.

So do I need to activate the system in order to configure MVSP and get it to spit out systemd service scripts?  (what about for telnet?  what generates that?)

Thanks folks!

g.

* by "golden master", I mean a fully configured RHEL 9 installation with D3 v10.3.4 installed, but not activated.

That 1.8.20 is NOT a patch. It's a full account-save of the MVSP account. There's a 1.8.21 available which I'm attaching hereto. Steps:

Make note of the MVSP-enabled accounts

Delete the MVSP account

RESTORE-ACCOUNTS from the pseudo (on D3 Windows, you would add an (R switch to get it into the FSI, but you're on Linux so not needed)

LOGTO the new MVSP account and go through the setup process if asked

Reenable the accounts that were previously MVSP-enabled

BTW, the Forum wouldn't let me upload a .d3p file, so I renamed MVSP_1.8.21.d3p to MVSP_1.8.21.txt. After you download, you can use it as-is, or rename it (my OCD would make me rename it).

I'm in the process of setting up a "golden master"[*] in order to migrate six D3 v9.0 Linux hosts to v10.3.4.

I wanted to get the base D3 install completed before turning the VM over to my infrastructure team for duplication.

I'm installing on RHEL 9 (9.4 specifically) and noticed that nothing has been done regarding systemd during the install process, even though there's some passing acknowledgement in the docs that xinetd is deprecated.  Nothing for telnet, nothing for MVSP.

I didn't know what to do regarding the missing systemd service scripts for telnet, (the word "systemd" doesn't even occur in the 10.3.4 installation guide.  That's problematic.), I figured I'd at least see if I could get MVSP set up - maybe that creates the systemd services.

I'm greeted with this:

:to mvsp

< Connect time= 0 Mins.; CPU= 0 Units; LPTR pages= 0        >
WHICH TCP/IP PORT NUMBER TO USE (9000) ?
DO YOU WANT AN SSL CONNECTION (Y/[N]) ?
Updating configuration. This could take upto 2 minutes to complete, please wait
INSTALL ERROR. CODE = 13
:

I'm going to assume that "13" means, "system not activated"?  If so, why doesn't it just say that?  If not, what on earth does "13" mean?

I should also point out that the MVSP v1.8.20 patch is among the D3 10.3.4 files, instead of with the other MVSP files but has no instructions regarding how the patch is applied.

The instructions for the ABS patch (at least a19) lists the wrong filename for the patch file.  The instructions call out linux1031a19, but the filename for the actual patch is lx64.10.3.x.a19.

So do I need to activate the system in order to configure MVSP and get it to spit out systemd service scripts?  (what about for telnet?  what generates that?)

Thanks folks!

g.

* by "golden master", I mean a fully configured RHEL 9 installation with D3 v10.3.4 installed, but not activated.

Brian, I'm having a problem when trying to attach the D3P file.  This is what I'm getting:

(my chg-device command is: chg-device 3 name=/mnt/backupstore/MVSP_1.8.21.D3P density=pseudo)

I've no idea why it's doing this.  The permissions on the tape file are 644 (rw owner, read for group & world)

Thanks!

g.

That 1.8.20 is NOT a patch. It's a full account-save of the MVSP account. There's a 1.8.21 available which I'm attaching hereto. Steps:

Make note of the MVSP-enabled accounts

Delete the MVSP account

RESTORE-ACCOUNTS from the pseudo (on D3 Windows, you would add an (R switch to get it into the FSI, but you're on Linux so not needed)

LOGTO the new MVSP account and go through the setup process if asked

Reenable the accounts that were previously MVSP-enabled

BTW, the Forum wouldn't let me upload a .d3p file, so I renamed MVSP_1.8.21.d3p to MVSP_1.8.21.txt. After you download, you can use it as-is, or rename it (my OCD would make me rename it).

I'm in the process of setting up a "golden master"[*] in order to migrate six D3 v9.0 Linux hosts to v10.3.4.

I wanted to get the base D3 install completed before turning the VM over to my infrastructure team for duplication.

I'm installing on RHEL 9 (9.4 specifically) and noticed that nothing has been done regarding systemd during the install process, even though there's some passing acknowledgement in the docs that xinetd is deprecated.  Nothing for telnet, nothing for MVSP.

I didn't know what to do regarding the missing systemd service scripts for telnet, (the word "systemd" doesn't even occur in the 10.3.4 installation guide.  That's problematic.), I figured I'd at least see if I could get MVSP set up - maybe that creates the systemd services.

I'm greeted with this:

:to mvsp

< Connect time= 0 Mins.; CPU= 0 Units; LPTR pages= 0        >
WHICH TCP/IP PORT NUMBER TO USE (9000) ?
DO YOU WANT AN SSL CONNECTION (Y/[N]) ?
Updating configuration. This could take upto 2 minutes to complete, please wait
INSTALL ERROR. CODE = 13
:

I'm going to assume that "13" means, "system not activated"?  If so, why doesn't it just say that?  If not, what on earth does "13" mean?

I should also point out that the MVSP v1.8.20 patch is among the D3 10.3.4 files, instead of with the other MVSP files but has no instructions regarding how the patch is applied.

The instructions for the ABS patch (at least a19) lists the wrong filename for the patch file.  The instructions call out linux1031a19, but the filename for the actual patch is lx64.10.3.x.a19.

So do I need to activate the system in order to configure MVSP and get it to spit out systemd service scripts?  (what about for telnet?  what generates that?)

Thanks folks!

g.

* by "golden master", I mean a fully configured RHEL 9 installation with D3 v10.3.4 installed, but not activated.