- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Delpen macro
Operating System - OpenVMS
1748180
Members
4187
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО05-11-2006 06:44 AM
тАО05-11-2006 06:44 AM
Re: Delpen macro
The link Dean sent is an example of a macro that prompts for the pid and then does it for you. The one mission critical gave us looks very similar. I'm a little rusty on macro. But I think this will work. I APPRECIATE EVERYONES RESPONSE TO USE WITH CAUTION CAN CAUSE CRASH. You never know what level of technical ability you will be giving responses to the person requesting. I have seen jr. systems people do these kind of things without thinking of the ramifications. But I know better. I will still post the example from mission critical once I can get some time to get it off one of my tapes.
The one difference is that again the mission critical macro you had to go into SDA and get the pcb;100 value and plug into the macro. But again they probably used this one as a base and tweaked it specifically for DTR users.
thanks
The one difference is that again the mission critical macro you had to go into SDA and get the pcb;100 value and plug into the macro. But again they probably used this one as a base and tweaked it specifically for DTR users.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2006 05:28 PM
тАО05-11-2006 05:28 PM
Re: Delpen macro
The one difference is that again the mission critical macro you had to go into SDA and get the pcb;100 value and plug into the macro
SDA> SET PROC/IND=
SDA> EXA pcb;100
will just dump the first 64. longword of the PCB. Maybe this was just used to obtain the PCB address (the last quadword on the first line displayed).
The macro program MNOWAIT referenced above obtains this address with the EXE$NAMPID internal system routine from the PID.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2006 06:30 AM
тАО05-12-2006 06:30 AM
Re: Delpen macro
I tried to enter this yesterday evening (Europe), but ITRC was fully dead till after bed-time.
Jthoma01, Volker:
THANKS a lot for adding another tool to my box!
Like you, we sometimes have processes that hang on to locks they should no longer hold, and refuse to be deleted bacause they wait for something that we know will never happen.
Reboot was the ultimate solution, but this tool slices another bit from that ugly lump.
And yes, I know the disclaimers about DELTA.
In a former life on ICL DME we also had a memory inspection-and-manipulation program. As a permanent warning, that program was named DYNAMITE and had to be LOADed from the BWAMM library. Talk about descriptive names!
Again:
MANY thanks. I hope to have little need for it, but WHEN, then I 'll remember you!
Proost.
Have one on me (maybe at the Bootcamp in Nashua?)
jpe
Jthoma01, Volker:
THANKS a lot for adding another tool to my box!
Like you, we sometimes have processes that hang on to locks they should no longer hold, and refuse to be deleted bacause they wait for something that we know will never happen.
Reboot was the ultimate solution, but this tool slices another bit from that ugly lump.
And yes, I know the disclaimers about DELTA.
In a former life on ICL DME we also had a memory inspection-and-manipulation program. As a permanent warning, that program was named DYNAMITE and had to be LOADed from the BWAMM library. Talk about descriptive names!
Again:
MANY thanks. I hope to have little need for it, but WHEN, then I 'll remember you!
Proost.
Have one on me (maybe at the Bootcamp in Nashua?)
jpe
Don't rust yours pelled jacker to fine doll missed aches.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP