Finishing Up

To restart your system on the backdated version, perform all the sub-sections in this section.

Configure Data Communication

Refer to "Configuring Datacomm and UPS" and "Cross Validating" in Chapter 6 “Finishing the Process” for additional information about these steps.




	CAUTION: No matter what your particular networking configuration is, whether you even have networked devices, you still must perform the activities described in this section.

You must convert the data communications configuration files after modifying a system (regardless of whether you use data communications products). The information contained in the data communication files is required by the Data communication Terminal Controller (DTC) and allows communication between the terminal and the Uninterruptible Power Supply (UPS). Refer to Using the Node Management Services Utilities.

Convert Data Communications

To configure for data communications on a new or modified system, obtain an NMCONFIG file in either way:

Convert an existing nmconfig file to the MPE 5.0 or 5.5 version level you are backdating to.
Create an NMCONFIG file using NMMGR. Do this if you are using either Method 2, "Using a factory SLT" or Method 3, "Using an FPT."

To convert data communications files:

Confirm that you have a copy of the NMCONFIG file on your system.
:LISTF NMCONFIG.PUB.SYS
- If listed, and you do not need to create a new NMCONFIG file, proceed to Step 2.
- If the return message is non-existent file, obtain a copy of an NMCONFIG file using one of the following sources:
  Create a new NMCONFIG file using nmmgr.
  Refer to Using the Node Management Services (NMS) Utilities for directions on creating an NMCONFIG file.
  Then proceed to "Cross Validate" in the next subsection.
  Use a backup copy of the NMCONFIG file.
  Use the same method, to recover the NMCONFIG file from the backup, that was used to create the backup.
  Then proceed to Step2.
Run the NMMGRVER conversion utility.
:RUN NMMGRVER.PUB.SYS
Enter NMCONFIG.PUB.SYS at the prompt:
FILESET TO BE SCANNED? NMCONFIG.PUB.SYS OK TO CONVERT NMCONFIG? Y
- If the return message is no need to convert, proceed to "Restart System Functions."
- If the return message is conversion completed successfully, then AUTOINST has converted your configuration file and it needs to be cross validated with sysgen information. Proceed to "Cross Validate."

Cross Validate

Perform the steps in this section if you did either of the following:

Completed the previous section, "Convert Data Communications," and your files were converted.
Created a new NMCONFIG file using nmmgr.

If the SYSGEN command, RDCC, was used previously, the network configuration file that was specified in that command is written to the CSLT that AUTOINST created. If this CSLT is used as a backup tape for a reinstallation, then the datacomm configuration file that will be restored will require conversion using the NMMGRVER.PUB.SYS utility after the installation.

To validate data communication files:

Run NMMGR.PUB.SYS
:NMMGR
Open the configuration file using the [F1] key.
Modify the configuration file, if required.
If you need to add, delete, or change any item in the configuration file, do so now. For example, now is the time to add a DTC or change a UPS configuration.
If you copied and updated your NMCONFIG file from another system, you must update the network addresses and other devices for this system.
1. If you have a PC-based network management configuration, follow the installation and configuration procedures described in the Using the OpenView DTC Manager Manual.
2. For information on NMMGR, refer to Using the Node Management Services (NM S) Utilities.
3. For information on configuring UPS devices, refer to Performing System Management Tasks.
4. If you need to configure new DTCs on your system or if you need more information on host-based network management, refer to Configuring Systems for Terminals, Printers, and Other Serial Devices.
Display the Validate screen and validate the DTSLINK, NS links, and any other configurations you have changed.
The specific method you use to view the Validate screen varies depending upon the procedures you used to modify the configuration file. Refer to the Using the Node Management Services (NM S) Utilities manual for more complete instructions.
NMMGR automatically invokes SYSGEN to cross validate the system and datacomm configurations.
If inconsistencies occur during the validation process (such as two separate devices configured to the same LDEV), do either of the following depending upon the type of error:
- Resolve them using NMMGR (if related to networking).
- Exit NMMGR, NMMGR to revalidate DTSLINK.
Exit NMMGR.

Preparing for Final Reboot

Before performing the final reboot, stream jconfjob and verify all activities for manually install products are complete.

To restart selected system functions:

If you purchased HP Resource Sharing and Information Access, install it now. Refer to Appendix A “Manually Installed Products”
Stream JCONFJOB.
:STREAM JCONFJOB.NET.SYS
The JCONFJOB.NET.SYS stream is required for all systems. It includes information files that describe the supported set of servers and services. These information files are used to build a configuration file called DADCONF.NET.SYS. Wait until the above jobstream is complete before continuing with the next step.

Set Passwords and Lockwords

Refer to "Setting Passwords and Lockwords" in Chapter 6 “Finishing the Process”

Set passwords for HP recommended accounts.
:ALTACCT acctname;PASS=password
AUTOINST does not require the removal of passwords. However, if these accounts and users do not have passwords, Hewlett-Packard recommends that you set them now.
Table D-2 Password Recommended HP Accounts
BIND
HPOFFICE
HPSKTS
JAVA
SYS
HPX11
CLL
HPOPTMGT
HPSPOOL
RJE
SYSLOG
NETWARE
CONV
HPPL85
INDHPE
SAMBA
SYSMGR
SOFTREP
HPLANMGR
HPPL87
INTSETUP
SNADS
TELESUP

HPNCS
HPPL89
ITF3000
SUPPORT
WWW
Set passwords for HP recommended users.
:ALTUSER username;PASS=password
These users were created or modified to have OP (System Supervisor) and/or PM (Privilege Mode) capabilities. Hewlett-Packard recommends that you set passwords for these users.
Table D-3 Password Recommended Users
MANAGER.SYS
FIELD. HPPL85
MGR.SNADS
MGR.JAVA
MGR.HPOFFICE
MGR.TELESUP
MGR.SYSMGR

Set passwords for MANAGER.SYS

:ALTACCT SYS;PASS=password
:ALTUSER MANAGER;PASS=password

Identify system files.

:SYSGEN
sysgen>SYSFILE
sysfile>SHOW

Record the list of files

sysfile>EXIT
sysgen>EXIT

Reapply or add lockwords to the system, as required.
If you removed any lockwords from the system earlier, reapply them now. Do not apply lockwords to system files.
:RENAME filename,filename/lockword
Review account security.
Refer to Controlling System Activity Manual and the HP Security Monitor/iX Managers Guide.
Reenter customized changes to CATALOG.PUB.SYS.

Enable UDCs

Refer to "Enabling UDCs" in Chapter 6 “Finishing the Process” for additional information about these steps.

Purge the command file:
:PURGE COMMAND.PUB.SYS
Enable UDCs.
:RENAME command_name,COMMAND.PUB.SYS
Where command_name is a temporary name you assigned the file. Refer to your task checklist for the temporary name of this file.
Set special UDCs, if your users plan to use POSIX features on MPE/iX.
:SETCATALOG HPPXUDC.PUB.SYS;SYSTEM;APPEND
Log on to activate the UDCs.
:HELLO MANAGER.SYS,INSTALL

Configure Manually Installed Products

Refer to Appendix A “Manually Installed Products” and the appropriate product manual for instructions. The products will not be operational until your perform the necessary configuration changes. Manually installed products include:

HP ALLBASE/4GL
ALLBASE/SQL or IMAGE/SQL
OpenView Console/System Manager
SNA IMF/iX
HP Predictive Support
Non-HP (Third Party) Software
Java/iX

Final Reboot

Refer to "Performing the Final Reboot" in Chapter 6 “Finishing the Process” for additional information about these steps.

Shutdown the system.
CTRL-A =SHUTDOWN
Reset the system.
As appropriate to your system, do either Step a or Step b:
1. For HP 3000 Series 991 or 995:
  CTRL-B CM>SP SP>RS
  Enter Y to HARD BOOT the computer system.
2. For all other systems:
  CTRL-B SP>RS
  If the system does not respond, press the reset button, key switch, or on/off switch as appropriate for your system.
  Enter Y to confirm restarting the system.
Boot the system from the primary boot path.
1. Boot messages can vary, depending on the system model.
2. Enter Y to the Interact with IPL? prompt, if it appears on your screen.
  The system boots from disk. After some activity the ISL prompt displays.
At the ISL prompt, enter:
ISL>START NORECOVERY
Confirm the date and time.
Log on.
:HELLO MANAGER.SYS;HIPRI

Restart System Functions

Refer to "Restarting Selected System Functions" in Chapter 6 “Finishing the Process” for additional information about any of these steps.

On local systems power cycle the DTCs. On remote systems reset DTCs.
If you are using OpenView DTC Manager, the DTCs do not need to be power cycled.
To power cycle all DTCs:
1. Turn DTC off.
2. Turn DTC on.
Power cycling each DTC enables the new download file and the DTC configurations to be downloaded to the DTC(s). To reset DTCs:
1. Type:
  :SYSDIAG DUI>TERMDSM
2. For each DTC, type:
  DUI>RESET DTCnn
  Where nn is the DTC number.

Purge groups.

:PURGEGROUP USL
:PURGEGROUP UXL
:PURGEGROUP UNL

Start data communications.
If you have NS 3000/iX configured, bring up the configured network interfaces. For more information, refer to the HP 3000/iX Network Planning, and Configuration Guide.
NOTE: Use the same names for the network interfaces that were used in your configuration.
- For example, if you have configured network interfaces with the names LOOP and LAN1, enter:
  :NETCONTROL START;NET=LOOP :NETCONTROL START;NET=LAN1 :NSCONTROL START :STREAM JFTPSTRT.ARPA.SYS
- If you have configured only the router network interface with the name ROUTER1, enter:
  :NETCONTROL START;NET=ROUTER1 :NSCONTROL START :STREAM JFTPSTRT.ARPA.SYS

Record the Backdate

The system is ready for normal production. Record the modification in the system logbook, noting the date and release to which you have modified the system. If you added subsystem products, note them in the log book including the release they are on.

If you need to add patches, contact your Response Center.