Hi Nipun,
May could I suggest a different solution approach?
First let us prioritise the problems.
So far I understood your feedback the DTSS is annoying but not a functional problem yet.
I configured a bunch of workstation in our clusters. And before trying to start Motif adjust some system parameters.
Therefore I do suggest to focus first on some system parameters that may prevent Motif (DEC-Windows) to start AND that the DECnet-Plus Protocol and TCP/IP Protocol are working (proper configured).
Here is my suggestion ordered by priority:
1) License check
2) System Parameters
3) Network Protocols (DECnet & TCP/IP)
4) Disabling DTSS
-----------------
A short question to some tools:
Do you work with PC's and connect to the OpenVMS Servers order do you work direct via Motif on the OpenVMS Servers?
On the PC's, do you have the VT Terminal Emulation Program installed such as PowerTerm or WRQ Reflection or KEA Term etc.?
PowerTerm is freely available from HP in the Layered Product Distribution => HP Pathworks 32
Using one of the Terminal Emulation Program is a real help. You can easily cut and past information to the system and for your documentation etc.
This enables you to cut and paste the suggestions directly and execute without missing a thing and the system response.
If you haven't the mentioned terminal emulation programs then C'est la vive. An issue for later.
Some notations: As you know the $-sign is the DCL Prompt. I will use it on some commands below. You don't have to type it in. It is just to identify this is a command.
WS = Workstation
-----------------
0) Prepare SIZZLE
Please logon SIZZLE...
Currently, I assume, you have only the console to work on the system?
A lot of messages appears and are very disturbing?
If so, and you would like to work on the console, enter following command:
$ REPLY /DISABLE
This will temporary disable the display of OPCOM messages such as DTSS etc. => IT WILL NOT SOLVE the problem!
Next you have to prepare the console (blue screen) for editing etc.:
$ SET TERMINAL / INSERT / INQUIRE
It will reply something with unknown terminal but it will work.
Now you should have just the DCL Prompt with a $ sign.
All further recommendations, is not otherwise noted, referring to SIZZLE
1) License Check
Now enter following License commands to make sure the NEW licenses of SIZZLE are proper assigned.
So far I followed you history you have registered the licenses successfully but these are not assigned to SIZZLE.
Before you start fetch your license paper you obtained with the DS25 (SIZZLE).
Mark each license certificate, for instance on the top right corner, with the node name SIZZLE (for sure with a pen so you can erase if needed).
This will help you to identify/distinguish later the licenses ;-))
Now we are ready, complete the commands below the product authorization number, often start with ILS... or ALS...:
$ LICENSE MODIFY NET-APP-SUP-150 /AUTHORIZATION=.... /INCLUDE=SIZZLE
$ LICENSE MODIFY OPEN3D /AUTHORIZATION=.... /INCLUDE=SIZZLE
$ LICENSE MODIFY OPENVMS-ALPHA /AUTHORIZATION=.... /INCLUDE=SIZZLE
$ LICENSE MODIFY OPENVMS-ALPHA-ADL /AUTHORIZATION=.... /INCLUDE=SIZZLE
$ LICENSE MODIFY PWLMXXXCA07.03 /AUTHORIZATION=.... /INCLUDE=SIZZLE
=> if you have more licenses for SIZZLE, but the licenses above are the most important once
$ LICENSE MODIFY ... /AUTHORIZATION=.... /INCLUDE=SIZZLE
In order to activate the changes we must reload the licenses
$ LICENSE LOAD
2) System Parameters
Motif but also DECnet-Plus and TCP/IP requires some adjustment to start successfully.
=> for details and verification refer to the installation of Motif on the OpenVMS DOC Web.
=> for details and verification refer to the installation of DECnet-Plus on the OpenVMS DOC Web.
=> for details and verification refer to the installation of TCP/IP on the OpenVMS DOC Web.
http://h71000.www7.hp.com/doc/os732_index.htmlBut here is a summary what should be ADDED: (append the values below but DO NOT replace the whole file except you fully understand what you do)
The MIN_ prefix in the MODPARAMS will have following affect:
- if the current calculated value of that parameter is lower then use the MIN_ value otherwise it will not affect the system
The ADD_ prefix in the MODPARAMS will have following affect:
- add the value of the ADD_parameter to the calculated value (increase)
Therefore after one successful AUTOGEN run change the ADD_ to MIN_
Refer to the OpenVMS Documentation for details =>
http://h71000.www7.hp.com/doc/os732_index.htmlSelect your Version of OpenVMS on the TAB
Then select Manual:
HP OpenVMS System Managerâ s Manual, Volume 2: Tuning, Monitoring, and Complex Systems
Chapter "Managing System Parameters"
Modify the system parameters by using MODPARAMS.DAT. The provided values are obtained from the installation guides.
Please note, this is just a jump start. Make your WS work. More tuning could be done later in a different discussion.
Are you familiar with the Editor? If NOT some advice: The Minus key (-) on the number keypad is by default defined as DO.
DO means you get the TPU command prompt. Here you enter EXIT for saving the changes or QUIT for NOT saving the changes.
For sure you can use the CTRL Z approach to save and exit the editor.
OpenVMS creates file versions and each exit will increase the counter and the file copy. The OS will use always the highest version number of a file.
$ EDIT SYS$SYSTEM:MODPARAMS.DAT
... already defined parameters ...
!! added 04-Apr-2005 by NIPUN
!!===================================================================
!!=> For HP TCP/IP Services for OpenVMS (Installation Guide)
!
ADD_NPAGEDYN = 500000
ADD_NPAGEVIR = 500000
ADD_GBLPAGES = 7500
ADD_GBLSECTIONS = 75
!
!!
!!===================================================================
!!=> For DECnet-Plus for OpenVMS Alpha (Installation Guide)
!
MIN_ARB_SUPPORT = 3
MIN_CLISYMTBL = 750
MIN_GBLPAGES = 100000
MIN_GBLPAGFIL = 1024
MIN_GBLSECTIONS = 512
MIN_KSTACKPAGES = 2
MIN_NPAGEDYN = 2100000
!
!!
!!===================================================================
!!=> For HP DECwindows Motif for OpenVMS Alpha (Installation Guide)
!
MIN_GBLSECTIONS = 6001
MIN_GBLPAGES = 1500001
MIN_GBLPAGFIL = 4096
MIN_SWPOUTPGCNT = 512
MIN_MAXBUF = 8192
ADD_CHANNELCNT = 255
MIN_PROCSECTCNT = 128
MIN_PQL_MASTLM = 100
MIN_PQL_MBIOLM = 100
MIN_PQL_MBYTLM = 100000
MIN_PQL_MDIOLM = 100
MIN_PQL_MENQLM = 300
MIN_PQL_MFILLM = 100
MIN_PQL_MPRCLM = 10
MIN_PQL_MWSDEFAULT = 1024
MIN_PQL_MWSQUOTA = 2048
MIN_PQL_MWSEXTENT = 8192
MIN_CLISYMTBL = 512
MIN_GH_RES_CODE = 1584
MIN_IMGREG_PAGES = 10000
MIN_WINDOW_SYSTEM = 1
MIN_NPAGEDYN = 1348576
MIN_PAGEDYN = 704288
MIN_WSMAX = 12000
!
!!
!!===================================================================
Save the changes as described above and activate them with the command below.
First we will test the new parameters => check the SYS$SYSTEM:AGEN$PARAMS.REPORT
$ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES noFEEDBACK
The mentioned report should NOT contain Errors and Fatal if so try to fix them or ask the community.
It will eventually complain the system uptime and some parameter duplications. At this time ignore this and proceed.
If the mentioned file looks OK then activate the new system parameters
(YES, this could be done easier. I prefer this approach because there is still a possibility to intervene...)
$ @SYS$UPDATE:AUTOGEN GETDATA SETPARAMS noFEEDBACK
Now reboot the WS => if you still have the original LOGIN.COM script then is there a symbol for the reboot defined.
Try:
$ REBOOT
If it is not working:
$ @SYS$SYSTEM:SHUTDOWN
Example:
$ @SYS$SYSTEM:SHUTDOWN
SHUTDOWN -- Perform an Orderly System Shutdown
on node SIZZLE
Do you really want to shutdown node SIZZLE [NO]? y
How many minutes until final shutdown [0]:
Reason for shutdown [Standalone]: HW Maintenance
Do you want to spin down the disk volumes [NO]?
Do you want to invoke the site-specific shutdown procedure [YES]? NO
Should an automatic system reboot be performed [NO]? YES
... => something like
Do you would like â [shortly via automatic reboot]â enter the default
When will the system be rebooted [later]:
Shutdown options (enter as a comma-separated list):
REMOVE_NODE Remaining nodes in the cluster should adjust quorum
CLUSTER_SHUTDOWN Entire cluster is shutting down
REBOOT_CHECK Check existence of basic system files
SAVE_FEEDBACK Save AUTOGEN feedback information from this boot
DISABLE_AUTOSTART Disable autostart queues
POWER_OFF Request console to power-off the system
Shutdown options [NONE]: REM,REB,SAV
%SHUTDOWN-I-BOOTCHECK, performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, basic reboot consistency check completed
%SHUTDOWN-I-SAVEFEED, saving AUTOGEN's feedback information from this boot...
%SHUTDOWN-I-SAVEOK, feedback info. saved in SYS$SYSTEM:AGEN$FEEDBACK.DAT
%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
%%%%%%%%%%% OPCOM 18-NOV-2004 01:02:35.41 %%%%%%%%%%%
Operator _SIZZLE$RTA1: has been enabled, username NIPUN
...
Refer to manual HP OpenVMS System Managerâ s Manual, Volume 1: Essentials
Page 122
=>>
http://h71000.www7.hp.com/doc/os732_index.html3) Network Protocols (DECnet & TCP/IP)
Are you able to successfully ping the cluster members and also a PC etc.
If not then you must configure TCP/IP
DECnet... Do you use DECnet over IP? If so then you must configure this as well.
Let me know if you need help.
I can provide you some sample installations in a separate file
==> Please so kind and provide us (community) feedback.
- Were the provided instructions helpful?
- How is the system status? Even if Motif is starting please verify the Network settings and let us know.
Monday evening I am available again.
Good luck and have a nice day.
OpenVMS Forever!
