I thought I should warn everyone preparing to update to 5.5 of a
particular problem.

Due to a limitation of a CM data structure (the LDT: Logical Device
Table) and a change in 5.5, if a printer or terminal profile in
NMCONFIG has a record width greater than 511 bytes, the system will
hang shortly after the DCC STARTUP message is printed on the console.

SR# 1653185041 has been submitted for the problem and is being
investigated. Note, the hang will occur during the first startup
after the UPDATE from the 5.5 SLT. It could also occur down the line
somewhere if someone changes a profile. This assumes an update from
5.0. If you are updating from 4.0, the hang will occur during the
first start-up following the conersion of the NMCONFIG file.

To get around the problem:

1. Restart the system using the following command which will prevent
   DCC STARTUP from occurring:

      ISL> START NORECOVERY SINGLE-USER LOGON=MANAGER.SYS

2. Identify the offending profile and change it:

         :file nmmgrcmd=$stdinx
         :nmmgr
         NMMGR>openconf nmconfig.pub.sys
         NMMGR>pathconf dts
         NMMGR>summaryconf dts profile

   This will generate a list of profile settings. Look for any whose
   "WIDTH" is greater than 511 and reduce them.

3. Validate the configuration. I prefer to exit NMMGR, reset the
   "nmmgrcmd" file equation, re-enter NMMGR, and then do the
   validation.

4. Shut the system down and perform a START NORECOVERY.


At this point you should be fine. If you need the additional record
width, you can use a file equation for the device or use the record
size parameter in the FOPEN call to override the NMMGR setting.

It is advisable you check the settings prior to an UPDATE but the
above steps will get you out of the situation in case you forget.

I hope this helps avoid an UPDATE delay for some of you.

--
                            --Pete Crosby
                              [log in to unmask]