Phil

Note that most system software products that show "SDSF DA" style information 
will most likely NOT be using the TIOT for anything related to address space 
identity.

Jobnames typically come from ASSBJBNS/JBNI or from the pointers in 
ASCBJBNS/JBNI or from whatever ERBSMFI returns for type 79-1 records.

Step and proc names tend to come from various CSCB fields depending on address 
space type.

Rob


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Phil Smith III
Sent: Wednesday, June 29, 2016 4:50 PM
To: [email protected]
Subject: JOB cards, procs, and TIOTs, o my!

Noticed something odd-ish. If you put a JOB card in a proc, the TIOT is 
populated differently, yet what SDSF;DA isn't quite what I'd expect. The 
behavior below has been observed on 1.12 and 2.1, all JES2.

That is, given a PROC called MYPROC, with no JOB card and a label of EXECIT on 
the EXEC PGM= card, doing S MYPROC shows:
JOBNAME  StepName ProcStep
MYPROC   MYPROC   EXECIT

So far so good. TIOCNJOB is MYPROC, TIOCSTPN (aka TIOCPSTN) is MYPROC.

Now instead we start it with S MYPROC.XXXX:
JOBNAME  StepName ProcStep
MYPROC   XXXX     EXECIT

Also as expected. TIOCNJOB is MYPROC, TIOCSTPN (aka TIOCPSTN) is XXXX.


Now insert a JOB card with a jobname of HAMSTER and issue S MYPROC:
JOBNAME  StepName ProcStep
HAMSTER  HAMSTER  EXECIT

Now TIOCNJOB is HAMSTER (as expected) but TIOCSTPN (aka TIOCPSTN) is EXECIT.
Yet SDSF;DA doesn't seem to reflect that--so clearly it's compensating for this 
weird case.


Finally, start the version with the JOB card as S MYPROC.XXXX:
JOBNAME  StepName ProcStep
HAMSTER  XXXX     EXECIT

Again, TIOCNJOB is HAMSTER but TIOCSTPN (aka TIOCPSTN) is EXECIT, and SDSF;DA 
shows the StepName as expected based on the Start command, but not based on 
TIOCSTPN/TIOCPSTN.


In all cases, TIOCJSTN -- the comment for which describes it as "8-BYTE JOBSTEP 
NAME FOR PROCS" -- seems to be blank.

Clearly SDSF is populating its list from a different set of blocks, which makes 
sense.

So my real point here is to articulate how inconsistent this is, and to ask 
three questions of the assembled wisdom:
1) Anyone know why TIOCJSTN is always blank, or perhaps a case where it isn't?
2) Can I determine programmatically whether the job is running as a job, as a 
proc, or as a proc with a JOB card?
3) Where can I find doc on what the effects are of adding a JOB card to a proc? 
(A customer did this, and while obviously I can ask him his reasons, I'd like 
to understand all the ramifications)

Thanks.

...phsiii

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN
================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
+1 877.328.2932 ■ +1 781.577.4321
Unsubscribe From Commercial Email – [email protected]
Manage Your Subscription Preferences - 
http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_SubscriptionCenter.html
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================

This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to