Jim,

I was referring to the fact that it is only GUPI for *MASTER* and no
other address space. 


Rob Scott
Rocket Software, Inc
275 Grove Street
Newton, MA 02466
617-614-2305
[EMAIL PROTECTED]
http://www.rs.com/portfolio/mxi_g2

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Jim Mulder
Sent: 25 January 2007 16:09
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Cross Memory and AR ASC Mode

IBM Mainframe Discussion List <IBM-MAIN@BAMA.UA.EDU> wrote on 01/25/2007
01:35:05 PM:

> Rob asks...
> > I have often wondered why ASSBSTKN is not GUPI as the values are 
> > guaranteed to be unique between IPLs. I remember asking IBM many 
> > years ago and was told that "it just wasn't, OK".

 From the SP5.1.0 IHAASSB macro:

*/*01* STATUS:  HBB5510
*/*
*/*01* EXTERNAL CLASSIFICATION: 
*/*02*         DMTI:BASE 
*/*02*         GUPI:FIELDS 
*/*                  ASSBEVST 
*/*                  ASSBVFAT 
*/*                  ASSBSTKN 
*/*                  ASSBWTCT 
*/*                  ASSBOASB 
*/*02*         PSPI:FIELDS 
*/*                  ASSBJBNI 
*/*                  ASSBJBNS 
*/*                  ASSBVAB 

> 
> Can you say "initiators" boys and girls?
> 
> The STOKEN for an address space does indeed remain unique for the life

> of the IPL, but many jobs run (serially) within an initiator and each 
> of those would "see" the same STOKEN value returned by EXTRACTH, or 
> just by snarfing it out of the ASSB.
> 
> But -logically- job 1 and job 2 are different things that just 
> happened to run in the same space. You would very likely land in two 
> wildly different places on successive SRB schedules. I suspect the 
> same issue exists for other "reused" address spaces such as BPXAS' and

> those ASCH thingies I've never had anything to do with.
> 
> Bottom line, just knowing the STOKEN - and even the jobname(!) isn't 
> really enough. You would have to use the STOKEN to at least get into 
> the right address space and when you "get there", do a little local 
> sniffing to decide if you're REALLY REALLY where you meant to be. The 
> details make this a tough little problem to crack on ones own eh?

  You could obtain and save the TTOKEN of the TCB pointed to by
ASCBXTCB.
At some point in the future, if the TTOKEN of the TCB pointed to by
ASCBXTCB matches the TTOKEN you save previously, then it is still the
same job step (because the TCB pointed to by ASCBXTCB terminates when a
job step terminates). 

Jim Mulder   z/OS System Test   IBM Corp.  Poughkeepsie,  NY

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to