On 3/5/2012 6:06 PM, Shmuel Metz (Seymour J.) wrote:
In<[email protected]>, on 03/04/2012
at 04:46 PM, Edward Jaffe<[email protected]> said:
Look more closely.
In the PLM that IBM doesn't publish?
Peter? Could you comment on what IGX00011 does?
To understand what it does study the two trace entries below (GTF is your
friend):
SVC CODE.... 109 ASCB.... 00F95200 CPU..... 0000
PSW..... 07850000 8000006D 00000000 0C53B222
TCB..... 00AC8300 R15..... 0000000B R0...... 00000000
R1...... 00000001
GMT-03/06/2012 06:59:08.693767 LOC-03/05/2012 22:59:08.693767
SVCR CODE.... 109 ASCB.... 00F95200 CPU..... 0000
PSW..... 07140000 8000006D 00000000 0C53B222
TCB..... 00AC8300 R15..... 00000000 R0...... 00000000
R1...... 00000001
GMT-03/06/2012 06:59:08.693799 LOC-03/05/2012 22:59:08.693799
You need to look more closely at IGX00011. Hint: the "secure"
implementation is not just in the SVC(ESR) routine itself but also
in the caller
What caller? It might not be the intended caller.
Of course, I meant the intended caller. Unintended callers can't successfully
use the service.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
310-338-0400 x318
[email protected]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
