|
The Special Registers 0 through 3 (SPRG0-3) are 64-bit registers. They are provided for general operating system use and can only be read/set in supervisor mode. SPRG1 contains the address of the currently executing task, which in turn has forwards/backwards links to all other tasks. Now, how does one get the contents of SPRG1? The active chain is indirectly pointed to from the Node Address Communications Area (NACA), which contains pointers to various system objects. The NACA is located at a fixed real address of '8000000000004000'. There is a lot more to this story, but here is not the place. ----- Original Message ----- From: Walden H. Leverich <WaldenL@TechSoftInc.com> To: <MI400@midrange.com> Sent: Tuesday, October 17, 2000 3:44 PM Subject: RE: Fighting cfint (academic quwstion) > In theory one would think you are correct. Since CFINT01 is implemented in > code one should be able to get around it. However, CFINT01 is a strange > task. It shows up in WRKSYSACT as a task, but I can't find a TDE for it in > SST. I can find other tasks, but not CFINT01. I'd bet IBM changed SST to > prevent CFINT from showing up. > > Does anyone know how to access the Task Dispatch List itself? I can see > entries from SST, but I want to see the hex in the TDL itself. CFINT01 > _must_ be in there for it to run, but I can't find the TDL. Any ideas? An > address would be great? Or an offset in the MISR or NACA +--- | This is the MI Programmers Mailing List! | To submit a new message, send your mail to MI400@midrange.com. | To subscribe to this list send email to MI400-SUB@midrange.com. | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dr2@cssas400.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.