HP3000-L Archives

December 2007, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Denys Beauchemin <[log in to unmask]>
Reply To:
Denys Beauchemin <[log in to unmask]>
Date:
Thu, 6 Dec 2007 17:40:34 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (168 lines)
What does :SHOWLOG display?

Denys...

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Marti Jarsey
Sent: Thursday, December 06, 2007 5:14 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] System Logging Error

Cheers Reid.

As you'll see in my response to Craig, there is currently only one log
file on the system.

But I did get some feedback from the status command:

LOGTOOL>status;detail
*** WARNING: SYSTEM LOGGING IS DISABLED (LTWARN 453)

Log File    Rec #1        Rec #1    Total
Name        Date          Time      #Records
==========  ============  ========  ========
LOG0390     12/03/07       8:43 PM    13897 

The text below is from sysgen>log>show command=all.  Is there somewhere
else that system logging could be disabled? 

        system log events             event #       status
        -----------------             -------       ------
        System Logging                    100           ON
        System Up                           101           ON
        Job Initiation                         102          OFF

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Reid E. Baxter
Sent: Thursday, December 06, 2007 3:05 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] System Logging Error

Marti,

By any chance have you restored log files to this server ? If you run
logtool and enter 'status;detail' do you see an incongruence in the
dates of the logfiles ? switchlog could be trying to fire up the next
logfile but it already exists (i.e. last log file was LOG0327, next is
LOG0328 but it already exists. The cure for this is to copy the logfiles
(LOG0328 and
after) out of pub or purge them. Then do a switchlog again. HTH

Regards,

Reid E. Baxter
Assistant Vice President
MPE/iX & UNIX Production Engineering
Commercial Banking - Technology Infrastructure JPMorgan Chase
Office: (614) 213-5321
Pager: (877) 482-0103
Pager E-Mail: [log in to unmask]


 

             Marti Jarsey

             <[log in to unmask]

             >
To 
             Sent by: HP-3000          [log in to unmask]

             Systems
cc 
             Discussion

             <[log in to unmask]
Subject 
             TC.EDU>                   [HP3000-L] System Logging Error

 

 

             12/06/2007 05:41

             PM

 

 

             Please respond to

               Marti Jarsey

             <[log in to unmask]

                     >

 

 





One of our servers is reporting the following error when we execute
switchlog.

:switchlog

NMEV#200@221 System logging is not enabled at the present time.

System Logging message 900

:


We've verified that system logging is enabled.  And I see current
console logs in the active log file.

The server is a 987 running POWERPATCH C6504 P4

Has anyone seen this before?

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


-----------------------------------------
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of any
financial instrument or as an official confirmation of any transaction.
All market prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice. Any
comments or statements made herein do not necessarily reflect those of
JPMorgan Chase & Co., its subsidiaries and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure under
applicable law. If you are not the intended recipient, you are hereby
notified that any disclosure, copying, distribution, or use of the
information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect that
might affect any computer system into which it is received and opened,
it is the responsibility of the recipient to ensure that it is virus
free and no responsibility is accepted by JPMorgan Chase & Co., its
subsidiaries and affiliates, as applicable, for any loss or damage
arising in any way from its use. If you received this transmission in
error, please immediately contact the sender and destroy the material in
its entirety, whether in electronic or hard copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2