topic Re: Wierd messages at boot in Operating System - OpenVMS

Wierd messages at boot

Fredrik.eriksson — Tue, 09 Jun 2009 11:25:13 GMT

Hi all :)

I have these somewhat wierd messages that doesn't really make any sense to me in my operator.log from the boot sequence.

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
RP: lp

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
SD: TCPIP$LPD_SPOOL

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
BP: TCPIP$LPD_QUEUE

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
PA: FALSE

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
ND: FALSE

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
CR: FALSE

%%%%%%%%%%% OPCOM 5-JUN-2009 18:19:34.09 %%%%%%%%%%
Message from user SYSTEM on NODE1
SN: FALSE

Does this tell anyone anything?

Best regards
Fredrik Eriksson

Re: Wierd messages at boot

marsh_1 — Tue, 09 Jun 2009 12:50:26 GMT

hi,

they look like entries from your ucx/tcpip$printcap.dat displayed during lpd startup.

fwiw

Re: Wierd messages at boot

Jim_McKinney — Tue, 09 Jun 2009 12:57:50 GMT

Found in the printcap file...

RP=remote printer
SD=spool directory
BP=banner program
PA=passall flag
ND=nodelete flag
CR=carriage return flag
SN=

Re: Wierd messages at boot

Fredrik.eriksson — Tue, 09 Jun 2009 12:59:24 GMT

So this basiclly just tells me what settings is set in the printcap file?

Best regards
Fredrik Eriksson

Re: Wierd messages at boot

Hoff — Tue, 09 Jun 2009 14:03:12 GMT

mayhap

http://h71000.www7.hp.com/doc/83final/6526/6526pro_055.html#pri_opcom_def_sec

?

Re: Wierd messages at boot

Wim Van den Wyngaert — Wed, 10 Jun 2009 07:02:10 GMT

I tried it with all LPD log options enabled. Got several messages but not yours. VMS 7.3, tcp 5.3 eco 2.

Any (undocumented) LPD logicals active ?

Wim

Re: Wierd messages at boot

Wim Van den Wyngaert — Wed, 10 Jun 2009 07:18:23 GMT

But of course it's not the service LPD that doing it. The outbound symbiont is doing it. Found the messages in tcpip$lpd_shr.exe.

Activated by TCPIP$LPD_RECV_DEBUG ?

Tried with value 1 but no success.

Wim

Re: Wierd messages at boot

Fredrik.eriksson — Wed, 10 Jun 2009 07:44:45 GMT

This is the only logical defined containting "lpd" i have.
"TCPIP$LPD_ROOT" = "DSA0:[SYS1.TCPIP$LPD.]"

This must be something that is set somewhere else :/

Thank you for all the replies so far :)

Best regards
Fredrik Eriksson

Re: Wierd messages at boot

Wim Van den Wyngaert — Wed, 10 Jun 2009 08:52:08 GMT

Did you try sh log *lpd*/tab=* ?
It could be given local to the process.

Wim

Re: Wierd messages at boot

marsh_1 — Wed, 10 Jun 2009 08:53:10 GMT

hi,

if there is nothing directly in systartup_vms.com do you call any other site-specific routines during startup that are doing things with print queue setup ?

fwiw

Re: Wierd messages at boot

Wim Van den Wyngaert — Wed, 10 Jun 2009 08:58:39 GMT

GOT IT ! Exectly the same messages.

def/sys/exec tcpip$lpd_symb_debug 15

Restart tcpip and you get the messages.
May be the logical is removed after the usage ?

Wim

Re: Wierd messages at boot

Wim Van den Wyngaert — Wed, 10 Jun 2009 09:10:30 GMT

7.3.1 release notes
TCPIP$LPD_DEBUG
LPD_DEBUG

Replaced by TCPIP$LPD_SYMB_DEBUG.

It was from 5.3 upwards.

Wim

Re: Wierd messages at boot

Fredrik.eriksson — Wed, 10 Jun 2009 09:41:32 GMT

So it's just debug messages?
Then i'll try to figure out what file is setting that logical since apperantly it will be set somewhere.

NODE1>sea dsa0:[*...]*.com "lpd_symb","lpd_debug"
%SEARCH-I-NOMATCHES, no strings matched

Seems somewhat elusive thou.

Best regards
Fredrik Eriksson

Re: Wierd messages at boot

Wim Van den Wyngaert — Wed, 10 Jun 2009 10:22:49 GMT

Which tcp version ?
Boots can be modified and can use ANY file for containing the command. Try *.*/excl=(*.exe,*.olb).

And of course one can do @ of something on another disk (we do).

Wim

Re: Wierd messages at boot

Hakan Zanderau ( Anders — Wed, 10 Jun 2009 11:54:52 GMT

The debugoptions for LPD have changed from logicals to options in TCPIP$LPD_ROOT:[000000]TCPIP$LPD.CONF in later versions of TCPIP.

Hakan

Re: Wierd messages at boot

Fredrik.eriksson — Wed, 10 Jun 2009 12:48:52 GMT

We're TCPIP V5.4-15 on OpenVMS 7.3-2 (we don't dare upgrade these machines :P).

Anyway, cannot find a tcpip$lpd.conf and searching throu all the files with excl=(*.exe,*.olb) did not yield any results.

I'm very certain that there are no boot files on other disks.

Can this be some default setting or something you can disable in the printcap file?

Best regards
Fredrik Eriksson

Re: Wierd messages at boot

Hakan Zanderau ( Anders — Wed, 10 Jun 2009 13:01:10 GMT

The Printcap-file just holds information about the queues. Nothing for the configuration of LPD.

What happens if you start LPD manually after boot ? Add an EXIT at the top of the LPD-startupfile.

Hmmmm..... does LPD work as expected ?

Hakan

Re: Wierd messages at boot

Fredrik.eriksson — Wed, 10 Jun 2009 13:10:31 GMT

I have tried to restart LPD on our test cluster (which also have these messages) without getting any of the messages I get from the boot.

I would try a real reboot, but sadly this is not possible since the developers needs them online.

LPD is working as expected yes.

Best regards
Fredrik Eriksson

Re: Wierd messages at boot

Hakan Zanderau ( Anders — Wed, 10 Jun 2009 16:04:47 GMT

Does your printcap-file look OK ?

Is there a queue called TCPIP$LPD_QUEUE ?

It's the queue where incoming LPD-jobs are placed by the LPDservice and processed before printcap is red for a target-queue.

In later versions the incomming queue is a generic queue called TCPIP$LPD_IN

Hakan

Du kan ringa mig for en muntlig diskussion om du vill..... 0501 - 353 26

Re: Wierd messages at boot

Wim Van den Wyngaert — Wed, 10 Jun 2009 17:16:10 GMT

In my vcersion stopping TCP didn't stop LPD symbionts. I had to stop/id. I think it(s a pure cliuent that hopes that TCP wil work again when the next reauest comes in.

Wim