- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- SYS$$QIO entries in System Service Call trace file
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
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
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
04-16-2013 02:41 AM
04-16-2013 02:41 AM
SYS$$QIO entries in System Service Call trace file
Tracing System Service Calls with set process/sslog I can see for example SYS$$QIO or other SYY$$* entries in the trace log.
Is there a difference between SYS$$QIO and SYS$QIO?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2013 03:47 PM
04-16-2013 03:47 PM
Re: SYS$$QIO entries in System Service Call trace file
Waving hands... the answer to "Is there a difference between SYS$$QIO and SYS$QIO?" is "not really".
The thing you refer to when you make a reference to SYS$QIO isn't a routine entry point. It's effectively an entry in a dispatch table, which is used to find the actual code (described in excruciating detail in the Internals and Data Structures manual, Section 7.5 CHANGE MODE DISPATCHING). There are several symbols associated with each system service, including the one prefixed SYS$$. The "$$" indicates an internal system defined symbol.
Somewhere around the web there's a paper written by Ruth Goldenberg which describes how system service tracing works. Ultimately, some address needs to be symbolised (basically a reverse lookup in a symbol table). Where that happens and which address is used will determine which symbol is chosen. As long as it's clear which system service is involved, I guess it doesn't matter how many $ signs are displayed.