Operating System - OpenVMS
1752794 Members
5903 Online
108789 Solutions
New Discussion юеВ

Re: unable to start LPD CLIENT

 
Jan van den Ende
Honored Contributor

Re: unable to start LPD CLIENT

Volker,

SET WATCH tell you exactly NOTHING. (rather surprising).

We have robooted one node, and the effect is that I do NOT have the error in the bootstrap (well, LPD was disabled).
Starting LPD gives the error again, and NO LPD queus can be started, because of the same error.

I could not find any old programs or procedures, but I can not be sure of that (how to recognise them?) But then again: it WAS running, and old stuff would have prevented it then as now.

:-( :-(

Proost.

Have one on me.

jpe

Don't rust yours pelled jacker to fine doll missed aches.
Volker Halle
Honored Contributor

Re: unable to start LPD CLIENT

Jan,

let me repeat the question: on which command or image do you get the error message ?

Something seems to be looking for a LPD_CLIENT entry in the service database. There is no such thing since TCPIP V5.1 ! Under previous versions, you had LPD/LPR under both the client and server menue in UCX$CONFIG.COM

Volker.
EdgarZamora
Trusted Contributor

Re: unable to start LPD CLIENT

Jan, can you give us a better idea of the environment (versions, cluster?, common system disk?) I'm thinking that some conversion steps may have been skipped in the past. Maybe the conversion step was only run on one node and you have to run it on the others, etc? Please give us details on the environment so we can analyze this better.

Volker Halle
Honored Contributor

Re: unable to start LPD CLIENT

Jan,


I could not find any old programs or procedures, but I can not be sure of that (how to recognise them?)


You're running TCPIP V5.4 ECO 4. Any TCPIP$* file older than around DEC-2003 (that's when TCPIP V5.4 first showed up on the LP CDs) may be 'too old'.

Volker.
Jan van den Ende
Honored Contributor

Re: unable to start LPD CLIENT

Volker,

I have been able to get output from SET WATCH.
The error is just after accessing TCPIP$LPD_UTILITIES, which attemps LIBRTL_D56_TV (status 1), then status 910 (??? isn't that file not found?), then TIE$MESSAGES.EXE , and the error display.

Does that tell you anything????

Proost.

Have one on me.

jpe

Don't rust yours pelled jacker to fine doll missed aches.
Volker Halle
Honored Contributor

Re: unable to start LPD CLIENT

Jan,

we're getting there...

Is the error on the

$ lpdutilities -f "START_SERVER_QUEUES"
or
$ lpdutilities -f "START_CLIENT_QUEUES"

command ?

Try SET WATCH FILE/CLASS=ALL to get more information.

Does the TCPIP$LPD_UTILITIES.EXE file look o.k. ?

Volker.
Jan van den Ende
Honored Contributor

Re: unable to start LPD CLIENT

Volker,

most of those are from 18-sep-2003; only SYS$EXAMPLES holds a lot of older stuff.

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Jan van den Ende
Honored Contributor

Re: unable to start LPD CLIENT

Volker,

$ lpdutilities -f "START_SERVER_QUEUES"

seeks and does NOT find TCPIP$LPD.CONF

then accesses TIE$MESSAGES.EXE

and gives the error.

AFAIK that .CONF is optional. It seems we never had it.

Does this help?

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
EdgarZamora
Trusted Contributor

Re: unable to start LPD CLIENT

Jan, could you supply the output of show logical tcpip$lpd* Thanks
Jan van den Ende
Honored Contributor

Re: unable to start LPD CLIENT

Edgar,

Two-site cluster, 2 nodes each site.
VMS 7.3-2, TCPIP V5.4 ECO 4
Common, shadowed 3 member system disk.
Most system control files (UAF, QUE, etc) off system disk on one cluster-common shadow set.
TCPIP 5.1 conversion executed on all 5 nodes (one has long since left, conversion was during that replacement period)

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.