- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- logging for services in TCPIP for VMS
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2006 06:39 AM
тАО10-02-2006 06:39 AM
Thanks for any & all assistance,
Dave
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2006 06:56 AM
тАО10-02-2006 06:56 AM
SolutionTCP/IP Services for OpenVMS Alpha Version
V5.4 - ECO 6"), but there seem to be hints
in SYS$MANAGER":TCPIP$CONFIG.COM, like:
/log=(file:sys$sysdevice:[TCPIP$bootp]TCPIP$bootp_run.log, all)
so I'd guess it's actually
/LOG_OPTIONS = FILE: log_file_spec
> [...] if I need to bounce the service [...]
I don't know, but I'd assume so. One way to
find out...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2006 07:37 PM
тАО10-02-2006 07:37 PM
Re: logging for services in TCPIP for VMS
http://h71000.www7.hp.com/doc/tcpip56.html
..in HTML or PDF format.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2006 07:47 PM
тАО10-02-2006 07:47 PM
Re: logging for services in TCPIP for VMS
SET SERVICE
/LOG_OPTIONS=
[ [NO]ACCEPT ]
[ [NO]ACTIVATE ]
[ [NO]ADDRESS ]
[ [NO]ALL ]
[ [NO]CONNECT ]
[ [NO]DEACTIVATE ]
[ [NO]ERROR ]
[ [NO]EXIT_CLEANUP ]
[ [NO]LOGIN ]
[ [NO]LOGOUT ]
[ [NO]MODIFY ]
[ [NO]REJECT ]
Sets the specified logging options for the service you are configuring.
The logging options have the following meanings:
Option Meaning
[NO]ACCEPT Message is logged when a request is accepted.
[NO]ACTIVATE Message is logged when the service is activated.
[NO]ADDRESS For auxiliary server messages and OpenVMS security
events, the message displays the IP address as a host
name. If host names are not relevant, HP recommends
that you specify [NO]ADDRESS.
[NO]ALL Messages are logged for all events.
[NO]CONNECT Message is logged when the auxiliary server issues a
connect request back to the client. The services that
usually make this request (on a second socket) are
remote shell and remote execute.
[NO]DEACTIVATE Message is logged when the service is being
deactivated.
[NO]ERROR Message is logged when an error is detected while
processing a request to the service.
[NO]EXIT_CLEANUP Message is logged when the service fails to complete
startup (that is, the server did not assign the BG
device, with logical name SYS$NET, or did not issue a
C socket before exiting).
[NO]LOGIN Message is logged when a connected terminal server
accepts a remote login request.
[NO]LOGOUT Message is logged when a connected terminal server
terminates a connection.
[NO]MODIFY Message is logged when the active service is being
modified.
[NO]REJECT Message is logged when a request is rejected.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2006 09:54 PM
тАО10-02-2006 09:54 PM
Re: logging for services in TCPIP for VMS
it (SYS$MANAGER:TCPIP$CONFIG.COM).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2006 11:32 AM
тАО10-03-2006 11:32 AM
Re: logging for services in TCPIP for VMS
Depending on your objective and version of TCPIP, TCPTRACE or TCPDUMP provide very detailed logs.
These are capture utilities, see the TCPIP Doc set at http://h71000.www7.hp.com/doc/tcpip56.html for more information. You can use Ethereal or the follow on Wireshark http://www.wireshark.org/ to view and manipulate the capture files.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2006 11:59 PM
тАО10-03-2006 11:59 PM
Re: logging for services in TCPIP for VMS
Andy, your first response was spot on!! And, just FYI: the service does need to be bounced to have the logging change take affect. Thanks also for the pointer to tcptrace and tcpdump. I have been using the tcptrace utility but didn't know about tcpdump.
Thanks again,
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-04-2006 12:01 AM
тАО10-04-2006 12:01 AM
Re: logging for services in TCPIP for VMS
Too early in the AM... ;-)