[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | PATHWORKS Troubleshooting Hints and Tips |
|
Moderator: | UTURBO::SWEEP |
|
Created: | Tue Dec 12 1995 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 59 |
Total number of notes: | 313 |
58.0. "Altstart mechanism" by UTRTSC::EISINK (No Kipling apes today) Fri Jun 06 1997 11:48
PATHWORKS has an alternative way to startup different components like
the server, daemon, master control process etc.
Mostly this is used to gather some trace information or to test/install
patches.
The following steps has to made :
Note : In a cluster we've only _one_ pwrk.ini file. So in a mixed
architecture cluster we hace to take that in account.
1) Create/edit pwrk$root:[000000]pwrk.ini
2) Add a new section [altstart]
3) Add the key for the component, for example lmsrv to startup
the pwrk$lmsrv process.
The following keys are valid:
LICENSE_R ! License registrar
LICENSE_S ! License server
LMSRV ! LAN Manager server
LMDMN ! Daemon
LMMCP ! Master Control process
LMRIPL ! Ripl.
MASTER ! MAster process
NBDAEMON ! Ancillary control process for Netbeui
KNBDAEMON ! Ancillary control process for TCP/IP
NETBIOS ! Netbios proces
4) Specify the startup command file for it, example:
[alstart]
lmsrv = device:[directory]pwrk$lmsrv_start.com
5) Create the startup command file and specify the image to run, like
$ create device:[directory]pwrk$lmsrv_start.com
$ run /nodebug device:[directory]pwrk$lmsrv.exe
Or in a mixed cluster:
$ set noon
$ ARCH_TYPE = f$getsyi("ARCH_TYPE")
$ if .not. $STATUS then ARCH_TYPE = 1 ! default is VAX
$ VAX = ARCH_TYPE .eq. 1
$ ALPHA = ARCH_TYPE .eq. 2
$ if VAX
$ then
$ run/nodebug device:[direcory]pwrk$lmsrv.exe_vax
$ else
$ run/nodebug device:[direcory]pwrk$lmsrv.exe_alpha
$ endif
Note the _nodebug_ switch. It must be specified.
When PATHWORKS is started the alternate component(s) is/are started.
T.R | Title | User | Personal Name | Date | Lines
|
---|