Re: Where is format of Job ID documented?

[Charles Mills]

Interesting. Thanks.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Ed Jaffe
Sent: Monday, July 04, 2016 3:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

On 6/15/2016 1:38 PM, Charles Mills wrote:
> Yeah, I know, JOBn or Tnnn.
>
> Is there a formal description somewhere? Where?

The reason the jobid is not documented is that it can be anything. 
Literally any values can be specified on the JOBNAME=, JOBID=, and USERID= 
keywords of the IAZXJSAB CREATE macro so, depending on which software product 
or component is creating the output, you could have all kinds of crazy values 
appear -- basically whatever naming convention works best for that product.

Most products don't do this, so their output inherits the values from the 
scheduled job. APPC/MVS and OMVS have been mentioned. APPC/MVS passes its own 
special TP jobname and TP jobid (Annn). OMVS passes its own special 
jobname, but simply propagates the JES jobid of the address space under which 
it happens to be running which means, if it's a BPXAS address space, you will 
get STCn/Snnn for JES2 and JOBn/Jnnn for JES3.

(E)JES provides an advanced feature, when copying spool output to sysout, that 
allows you to propagate identification information from the original job, which 
facilitates -- among other things -- JES-generated banner pages similar to the 
original. To illustrate my point, I did a temporary recompile specifying 
JOBNAME==C'YOURENOT' and JOBID==C'CRAZYBOY' and the result displayed in (E)JES 
was:

OUTPUT   2,290S  2,225J  45T  9,415,891 Records (0 Sched)  88 Pages
Command ===>
Cmd JobName  JobIDStatus  C Pri Dest  ODisp Records
---  /--- - --- - - --
 YOURENOT CRAZYBOY QUEUED  T 144 LOCAL WRITE 87

STATUS   2,290S  61X  2,402W  1H  45T  9,777,431 Records  88 Pages
Command ===>
Cmd JobName  JobIDStatus QueueJP Pos Records
---  /--  -- --- --
 YOURENOT CRAZYBOY QUEUED PRINT15  2K 87

The JES2 DISPLAY command output shows:

$HASP686 OUTGRP=YOURENOT.1.1,BURST=NO,FCB=,
$HASP686 FLASH=,FORMS=STD,HOLD=(NONE),
$HASP686 OUTDISP=WRITE,PRIORITY=144,
$HASP686 PRMODE=LINE,QUEUE=T,
$HASP686 RECORDS=(87 OF 87),ROUTECDE=LOCAL,
$HASP686 SECLABEL=,TPJOBID=CRAZYBOY,
$HASP686 TPJOBN=YOURENOT,TSOAVAIL=NO,UCS=,
$HASP686 USERID=EDJAFFE,WRITER=

I didn't try this under JES3 but, trust me, you will get similar results.

Even SDSF is able to display this information on the OUTPUT display.

SDSF OUTPUT ALL CLASSES ALL FORMSLINES 9,415,891   LINE 3341-3401 (3451)
COMMAND INPUT ===> SCROLL ===> CSR
NP   JOBNAME  JobIDOwnerPrty C FormsDest Tot-Rec
  YOURENOT CRAZYBOY EDJAFFE   144 T STD LOCAL 87

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Ed Jaffe]

On 6/15/2016 1:38 PM, Charles Mills wrote:

Yeah, I know, JOBn or Tnnn.

Is there a formal description somewhere? Where?


The reason the jobid is not documented is that it can be anything. 
Literally any values can be specified on the JOBNAME=, JOBID=, and 
USERID= keywords of the IAZXJSAB CREATE macro so, depending on which 
software product or component is creating the output, you could have all 
kinds of crazy values appear -- basically whatever naming convention 
works best for that product.


Most products don't do this, so their output inherits the values from 
the scheduled job. APPC/MVS and OMVS have been mentioned. APPC/MVS 
passes its own special TP jobname and TP jobid (Annn). OMVS passes 
its own special jobname, but simply propagates the JES jobid of the 
address space under which it happens to be running which means, if it's 
a BPXAS address space, you will get STCn/Snnn for JES2 and 
JOBn/Jnnn for JES3.


(E)JES provides an advanced feature, when copying spool output to 
sysout, that allows you to propagate identification information from the 
original job, which facilitates -- among other things -- JES-generated 
banner pages similar to the original. To illustrate my point, I did a 
temporary recompile specifying JOBNAME==C'YOURENOT' and 
JOBID==C'CRAZYBOY' and the result displayed in (E)JES was:


OUTPUT   2,290S  2,225J  45T  9,415,891 Records (0 Sched)  88 Pages
Command ===>
Cmd JobName  JobIDStatus  C Pri Dest  ODisp Records
---  /--- - --- - - --
YOURENOT CRAZYBOY QUEUED  T 144 LOCAL WRITE 87

STATUS   2,290S  61X  2,402W  1H  45T  9,777,431 Records  88 Pages
Command ===>
Cmd JobName  JobIDStatus QueueJP Pos Records
---  /--  -- --- --
YOURENOT CRAZYBOY QUEUED PRINT15  2K 87

The JES2 DISPLAY command output shows:

$HASP686 OUTGRP=YOURENOT.1.1,BURST=NO,FCB=,
$HASP686 FLASH=,FORMS=STD,HOLD=(NONE),
$HASP686 OUTDISP=WRITE,PRIORITY=144,
$HASP686 PRMODE=LINE,QUEUE=T,
$HASP686 RECORDS=(87 OF 87),ROUTECDE=LOCAL,
$HASP686 SECLABEL=,TPJOBID=CRAZYBOY,
$HASP686 TPJOBN=YOURENOT,TSOAVAIL=NO,UCS=,
$HASP686 USERID=EDJAFFE,WRITER=

I didn't try this under JES3 but, trust me, you will get similar results.

Even SDSF is able to display this information on the OUTPUT display.

SDSF OUTPUT ALL CLASSES ALL FORMSLINES 9,415,891   LINE 3341-3401 (3451)
COMMAND INPUT ===> SCROLL ===> CSR
NP   JOBNAME  JobIDOwnerPrty C FormsDest Tot-Rec
 YOURENOT CRAZYBOY EDJAFFE   144 T STD LOCAL 87

HTH

--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

FW: Where is format of Job ID documented?

[Barry Merrill]

One addition for the archives for this thread:

 SMF 6 records written by PRINTWAY/INFOPRINT BASIC Mode contain
JCTJOBID='PSnn'.

 (which could be confused with type 6 records written by PSF, which contain
PSFn).

Barry


Merrilly yours,

 Herbert W. Barry Merrill, PhD
 President-Programmer
 Merrill Consultants
 MXG Software
 10717 Cromwell Drive  technical questions: supp...@mxg.com
 Dallas, TX 75229
 http://www.mxg.comadmin questions: ad...@mxg.com
 tel: 214 351 1966
 fax: 214 350 3694

 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Barry Merrill
Sent: Wednesday, June 15, 2016 3:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

NO, but MXG has discovered these possibilities:


/* THIS ROUTINE EXPECTS JCTJOBID AND JOB AS 8-BYTE CHARACTERS, */
 /* AND SUBSYS AS A 4-BYTE CHARACTER AS INPUT.  */

 /* JCTJOBID OF ONE LETTER AND 7 DIGITS EXIST, BUT THE MAXIMUM  */
 /* JESNR IS 99 BECAUSE THE 1ST WHEN SEVEN IS ALWAYS ZERO.  */

 /* IT CREATES THE 4-BYTE CHARACTER TYPETASK AND NUMERIC JESNR  */
 /* IT IS %INCLUDE-D AFTER JCTJOBID AND SUBSYS EXIST.   */

 TYPETASK='';
 JESNR=.;
 IF SUBSYS=''  THEN SUBSYS=''; /*EARLY ASIDS,TMNT */
 IF JCTJOBID=JOB OR (JCTJOBID LE ' ' AND SUBSYS='STC')
 OR (JCTJOBID EQ 'MSTR' AND SUBSYS='SMS') THEN DO;
   JESNR=.;
   TYPETASK='STC';
 END;
 ELSE DO;
   IF INPUT(SUBSTR(JCTJOBID,2,7),?? 7.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,2,7),?? 7.);
 TYPETASK=SUBSTR(JCTJOBID,1,1);
   END;
   ELSE IF INPUT(SUBSTR(JCTJOBID,3,6),?? 6.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,3,6),?? 6.);
 TYPETASK=SUBSTR(JCTJOBID,1,2);
   END;
   ELSE IF INPUT(SUBSTR(JCTJOBID,4,5),?? 5.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,4,5),?? 5.);
 TYPETASK=SUBSTR(JCTJOBID,1,3);
   END;
   ELSE IF INPUT(SUBSTR(JCTJOBID,5,4),?? 4.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,5,4),?? 4.);
 TYPETASK=SUBSTR(JCTJOBID,1,4);
   END;
   IF SUBSYS='TCP ' THEN TYPETASK='TCP ';
   ELSE IF SUBSYS='PSF ' THEN TYPETASK='PSF ';
   ELSE IF SUBSYS='VPS ' THEN TYPETASK='VPS ';
   ELSE IF TYPETASK=:'J' THEN DO;
 IF  SUBSYS='TSO ' THEN TYPETASK='TSU ';
 ELSE IF SUBSYS='JES2' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='JES3' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='STC ' THEN TYPETASK='STC ';
 ELSE IF SUBSYS='OMVS' THEN TYPETASK='OMVS';
 ELSE   TYPETASK='JOB ';
   END;
   ELSE IF TYPETASK=:'O' OR SUBSYS='OMVS' THEN TYPETASK='OMVS';
   ELSE IF TYPETASK=:'G' THEN TYPETASK='JOBG';
   ELSE IF TYPETASK=:'S' THEN TYPETASK='STC ';
   ELSE IF TYPETASK=:'A' THEN TYPETASK=SUBSYS;/*ASCH-OR-OMVS:CH16.150*/
   ELSE IF TYPETASK=:'T' THEN TYPETASK='TSU ';
   ELSE IF TYPETASK=:'I' AND SUBSYS='STC' THEN TYPETASK='STC  ';
   ELSE DO;
 IF  SUBSYS='STC ' THEN TYPETASK='STC ';
 ELSE IF SUBSYS='TSO ' THEN TYPETASK='TSU ';
 ELSE IF SUBSYS='JES2' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='JES3' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='STC ' THEN TYPETASK='STC ';
 ELSE IF SUBSYS='OMVS' THEN TYPETASK='OMVS';
 ELSE DO;
   IF PRODUCT='' THEN PRODUCT='';;
   IF SUBTYPE=.  THEN SUBTYPE=.;
   IF PRODUCT='PERFMON ' AND SUBTYPE=3 THEN DO;
 TYPETASK='STC';
 SUBSYS='PERFMON';
       END;
     END;
   END;
   IF TYPETASK=' ' THEN DO;
 BADVJESN+1;
 IF BADVJESN LE 2 THEN
   PUT '*** WARNING - TYPETASK NOT DECODED: ' /  +10
   _N_= SYSTEM= ID= SUBTYPE= JOB=
   JCTJOBID= SUBSYS= TYPETASK= JESNR= ;
   END;
   &MACJESN;
 END;
  /* END OF MEMBER VGETJESN - GET JESNR AND TYPETASK FROM JCTJOBID */

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Charles Mills
Sent: Wednesday, June 15, 2016 3:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Where is format of Job ID documented?

Yeah, I know, JOBn or Tnnn.

Is there a formal description somewhere? Where?

Charles 

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Mark Zelden]

I meant to add one other point before I posted, but forgot.   Someone mentioned
having to do "something" to purge these APPC jobs.   If you have regular "mass" 
purge
commands scheduled by some automation (for example $OJOBQ, $PJOBQ, or
$POJOBQ) in order to purge APPC output you need to add the ",PROTECTED" operand 
to the command(s).  All APPC output is protected - as are OMVS "thingies" (lol) 
like BPXAS.

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/


On Mon, 20 Jun 2016 13:44:37 -0500, Mark Zelden  wrote:

>On Mon, 20 Jun 2016 18:16:54 +, Jesse 1 Robinson  
>wrote:
>
>>I see the same thing as Mark. (What is LL?) I had previously ignored ASCHINTs 
>>because
>>they were STC. So what happens to the TPJOBID Annn ? Are they real spool 
>>thingies? 
>
>LL just adds ",long" to the display ("list long").They are real spool 
>"thingies".  They are
>output groups associated with the ASCHINT STC.   They are assigned the Annn
>TPJOBID.   Who knows what this looked like "back in the day" compared to now 
>from
>a JES2 standpoint.  I guess I would have to dig up some old JES2 manuals and 
>see
>if there was such an animal as TPJOBID.   I don't have time.  :-)   
>
>So to bring this full circle, even though SDSF displays these output groups as
>an Ann jobname and the numbers appear to be counted and even reset
>like normal job numbers (my client resets the job numbers every shift for
>some archaic reason to know what shift a job ran on and I see Annn also
>reset), there are actually only 2 flavors  -  JOBn/Jnnn and
>STCn/Snnn.   The RANGE= parm for JOBDEF mentioned in
>an earlier post doesn't need a doc update after all.   
>
>Regards,
>
>Mark
>--
>Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
>ITIL v3 Foundation Certified
>mailto:m...@mzelden.com
>Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
>Systems Programming expert at http://search390.techtarget.com/ateExperts/
>
>
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Mark Zelden]

On Mon, 20 Jun 2016 18:16:54 +, Jesse 1 Robinson  
wrote:

>I see the same thing as Mark. (What is LL?) I had previously ignored ASCHINTs 
>because
>they were STC. So what happens to the TPJOBID Annn ? Are they real spool 
>thingies? 

LL just adds ",long" to the display ("list long").They are real spool 
"thingies".  They are
output groups associated with the ASCHINT STC.   They are assigned the Annn
TPJOBID.   Who knows what this looked like "back in the day" compared to now 
from
a JES2 standpoint.  I guess I would have to dig up some old JES2 manuals and see
if there was such an animal as TPJOBID.   I don't have time.  :-)   

So to bring this full circle, even though SDSF displays these output groups as
an Ann jobname and the numbers appear to be counted and even reset
like normal job numbers (my client resets the job numbers every shift for
some archaic reason to know what shift a job ran on and I see Annn also
reset), there are actually only 2 flavors  -  JOBn/Jnnn and
STCn/Snnn.   The RANGE= parm for JOBDEF mentioned in
an earlier post doesn't need a doc update after all.   

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Jesse 1 Robinson]

I see the same thing as Mark. (What is LL?) I had previously ignored ASCHINTs 
because they were STC. So what happens to the TPJOBID Annn ? Are they real 
spool thingies?

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mark Zelden
Sent: Monday, June 20, 2016 6:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Where is format of Job ID documented?

So I was looking at some of this APPC output getting purged and noticed that 
the jobname purged is always ASCHINT with an STC job number.

I displayed one of the jobs in the spool by putting an LL next to the output in 
SDSF and the Annn jobid I see in SDSF is displayed as the "TPJOBID" in the 
output.

MZELDEN  0210  $DOS(30087),OUTGRP=ITIMCMD.1.1,LONG  
   
STC30087 0211  $HASP686 OUTPUT(ASCHINT) 154 
   
 154 0211  $HASP686 OUTPUT(ASCHINT)   
OUTGRP=ITIMCMD.1.1,BURST=NO,FCB=,
 154 0211  $HASP686   FLASH=,FORMS=STD,HOLD=(NONE), 
   
 154 0211  $HASP686   
OFFS=(),OUTDISP=HOLD,PRIORITY=144,   
 154 0211  $HASP686   PRMODE=LINE,QUEUE=Y,RECORDS=(6 OF 
6),
 154 0211  $HASP686   ROUTECDE=LOCAL,SECLABEL=, 
   
 154 0211  $HASP686   TPJOBID=A0004237,TPJOBN=ITIMCMD,  
   
 154 0211  $HASP686   
TSOAVAIL=YES,UCS=,USERID=ITIAGNT,
 154 0211  $HASP686   WRITER=,REBUILD=NO,   
   
 154 0211  $HASP686   CRTIME=(2016.170,07:04:21)   


Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 
Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: 
http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/



On Mon, 20 Jun 2016 03:52:33 -0500, Barry Merrill  wrote:

> FWIW, this old change does document the actual existence of JCTJOBID='A':
>
> Change 08.224  Support for MVS/ESA 4.2 (RMF 4.2.1).
> Jan 28, 1991
>
>   d. The JCTJOBID field from which TYPETASK and JESNR are
>  extracted has changed with APPC.  Instead of three
>  characters JOB/STC/TSU follwed by the five digit JESNR
>  the JCTJOBID will contain an "A" and a seven digit
>  number, which MXG stores in TYPETASK and JESNR, but
>  the maximum JESNR is 999,999 because the first of the
>  seven digits is always a zero.  You should check if
>  any reporting programs use TYPETASK for selection, and
>  to ensure they are coded robustly so they will not
>  fail if TYPETASK='A' is encountered.  The JCTJOBID
>  change was not compatibly implemented and changed
>  VMAC6,VMAC30,VMAC32,VMAC26J2, and VMAC26J3.  SMF
>  records use the fieldname SMFnnJNM for the eight byte
>  JCTJOBID field.  This IBM change in that field could
>  also affect "banner page" printing code in your SMF
>  exits.
>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
>On Behalf Of Mark Zelden
>Sent: Sunday, June 19, 2016 1:47 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Where is format of Job ID documented?
>
>On Sat, 18 Jun 2016 21:00:38 +, Jesse 1 Robinson  
>wrote:
>
>>How could I determine if APPC output is clogging my spool? I don't see any at 
>>the moment. 
>
>Set PREFIX=* ,  DEST= (null)  and OWNER=* in SDSF.
>
>Issue "H ALL"  and sort on JOBID and look for Annn Issue "O" and 
>sort on JOBID and look for Annn
>
>This assumes you don't have any SDSF parms or SDSF SAF security rules 
>preventing you from seeing the output.  
>
>Regards,
>
>Mark
>--
>Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 
>Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: 
>http://www.mzelden.com/mvsutil.html
>Systems Programming expert at 
>http://search390.techtarget.com/ateExperts/


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Mark Zelden]

So I was looking at some of this APPC output getting purged and noticed
that the jobname purged is always ASCHINT with an STC job number.

I displayed one of the jobs in the spool by putting an LL next to the output in
SDSF and the Annn jobid I see in SDSF is displayed as the "TPJOBID" in the 
output.

MZELDEN  0210  $DOS(30087),OUTGRP=ITIMCMD.1.1,LONG  
   
STC30087 0211  $HASP686 OUTPUT(ASCHINT) 154 
   
 154 0211  $HASP686 OUTPUT(ASCHINT)   
OUTGRP=ITIMCMD.1.1,BURST=NO,FCB=,
 154 0211  $HASP686   FLASH=,FORMS=STD,HOLD=(NONE), 
   
 154 0211  $HASP686   
OFFS=(),OUTDISP=HOLD,PRIORITY=144,   
 154 0211  $HASP686   PRMODE=LINE,QUEUE=Y,RECORDS=(6 OF 
6),
 154 0211  $HASP686   ROUTECDE=LOCAL,SECLABEL=, 
   
 154 0211  $HASP686   TPJOBID=A0004237,TPJOBN=ITIMCMD,  
   
 154 0211  $HASP686   
TSOAVAIL=YES,UCS=,USERID=ITIAGNT,
 154 0211  $HASP686   WRITER=,REBUILD=NO,   
   
 154 0211  $HASP686   CRTIME=(2016.170,07:04:21)   


Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/



On Mon, 20 Jun 2016 03:52:33 -0500, Barry Merrill  wrote:

> FWIW, this old change does document the actual existence of JCTJOBID='A':
>
> Change 08.224  Support for MVS/ESA 4.2 (RMF 4.2.1).
> Jan 28, 1991
>
>   d. The JCTJOBID field from which TYPETASK and JESNR are
>  extracted has changed with APPC.  Instead of three
>  characters JOB/STC/TSU follwed by the five digit JESNR
>  the JCTJOBID will contain an "A" and a seven digit
>  number, which MXG stores in TYPETASK and JESNR, but
>  the maximum JESNR is 999,999 because the first of the
>  seven digits is always a zero.  You should check if
>  any reporting programs use TYPETASK for selection, and
>  to ensure they are coded robustly so they will not
>  fail if TYPETASK='A' is encountered.  The JCTJOBID
>  change was not compatibly implemented and changed
>  VMAC6,VMAC30,VMAC32,VMAC26J2, and VMAC26J3.  SMF
>  records use the fieldname SMFnnJNM for the eight byte
>  JCTJOBID field.  This IBM change in that field could
>  also affect "banner page" printing code in your SMF
>  exits.
>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
>Behalf Of Mark Zelden
>Sent: Sunday, June 19, 2016 1:47 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Where is format of Job ID documented?
>
>On Sat, 18 Jun 2016 21:00:38 +, Jesse 1 Robinson  
>wrote:
>
>>How could I determine if APPC output is clogging my spool? I don't see any at 
>>the moment. 
>
>Set PREFIX=* ,  DEST= (null)  and OWNER=* in SDSF.
>
>Issue "H ALL"  and sort on JOBID and look for Annn Issue "O" and sort on 
>JOBID and look for Annn
>
>This assumes you don't have any SDSF parms or SDSF SAF security rules 
>preventing you from seeing the output.  
>
>Regards,
>
>Mark
>--
>Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 
>Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: 
>http://www.mzelden.com/mvsutil.html
>Systems Programming expert at http://search390.techtarget.com/ateExperts/
>--
>For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
>lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Barry Merrill]

 FWIW, this old change does document the actual existence of JCTJOBID='A':

 Change 08.224  Support for MVS/ESA 4.2 (RMF 4.2.1).
 Jan 28, 1991

   d. The JCTJOBID field from which TYPETASK and JESNR are
  extracted has changed with APPC.  Instead of three
  characters JOB/STC/TSU follwed by the five digit JESNR
  the JCTJOBID will contain an "A" and a seven digit
  number, which MXG stores in TYPETASK and JESNR, but
  the maximum JESNR is 999,999 because the first of the
  seven digits is always a zero.  You should check if
  any reporting programs use TYPETASK for selection, and
  to ensure they are coded robustly so they will not
  fail if TYPETASK='A' is encountered.  The JCTJOBID
  change was not compatibly implemented and changed
  VMAC6,VMAC30,VMAC32,VMAC26J2, and VMAC26J3.  SMF
  records use the fieldname SMFnnJNM for the eight byte
  JCTJOBID field.  This IBM change in that field could
  also affect "banner page" printing code in your SMF
  exits.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mark Zelden
Sent: Sunday, June 19, 2016 1:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

On Sat, 18 Jun 2016 21:00:38 +, Jesse 1 Robinson  
wrote:

>How could I determine if APPC output is clogging my spool? I don't see any at 
>the moment. 

Set PREFIX=* ,  DEST= (null)  and OWNER=* in SDSF.

Issue "H ALL"  and sort on JOBID and look for Annn Issue "O" and sort on 
JOBID and look for Annn

This assumes you don't have any SDSF parms or SDSF SAF security rules 
preventing you from seeing the output.  

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 
Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: 
http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Mark Zelden]

On Sat, 18 Jun 2016 21:00:38 +, Jesse 1 Robinson  
wrote:

>How could I determine if APPC output is clogging my spool? I don't see any at 
>the moment. 

Set PREFIX=* ,  DEST= (null)  and OWNER=* in SDSF.

Issue "H ALL"  and sort on JOBID and look for Annn
Issue "O" and sort on JOBID and look for Annn

This assumes you don't have any SDSF parms or SDSF SAF security rules preventing
you from seeing the output.  

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Mark Zelden]

On Sat, 18 Jun 2016 08:05:02 -0500, Joel C. Ewing  wrote:

>We always auto-purged older held output known to be past its usefulness
>and for some categories of output that usefulness was a matter of hours
>not days.
>
>My recollection is that after APPC came upon the scene we had to modify
>the held-output purge command sequences or APPC output wasn't touched.
>Makes me wonder if the folks seeing terrible performance when SDSF shows
>APPC output could be unintentionally retaining APPC junk in their output
>queue that has no useful function and which would be better to purge in
>a more timely fashion.
>Joel C Ewing


From what I recall, having APPC ON desegregated performance whether you had
APPC output or not.   Testing with "APPC ON" right now in a fairly large 
spool environment doesn't seem to hurt performance at all.   I recall doing
the same test some years ago with the same results.  So that leads me
to believe the original problem was fixed in either SDSF or maybe it was 
fixed as a result of a change in JES2.   However, "this ain't 1992" either. 
The processors are so much faster, I have no way of knowing for sure
if the original problem was really "fixed" or not.

 
Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Joel C. Ewing]

There are ways in SDSF (I don't remember the details and they may have
changed) for someone with sufficient authority to display everything in
the output queues (STATUS ALL comes to mind, but it's been too long). 
If you find many Annn JOBID entries, especially with old dates, you
may have a problem.  If your installation doesn't intentionally support
any APPC apps, I wouldn't think you would find any. 

Unless things have changed.   APPC isn't functional by default but
requires an installation to take deliberate action to set up several
configuration files to define the APPC transactions to make it
functional.  If that hasn't been done, I wouldn't expect any APPC output
to exist.
Joel C Ewing

On 06/18/2016 04:00 PM, Jesse 1 Robinson wrote:
> How could I determine if APPC output is clogging my spool? I don't see any at 
> the moment.
>
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler 
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-302-7535 Office
> robin...@sce.com
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Joel C. Ewing
> Sent: Saturday, June 18, 2016 6:05 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: Where is format of Job ID documented?
>
> We always auto-purged older held output known to be past its usefulness and 
> for some categories of output that usefulness was a matter of hours not days. 
>
> My recollection is that after APPC came upon the scene we had to modify the 
> held-output purge command sequences or APPC output wasn't touched. 
> Makes me wonder if the folks seeing terrible performance when SDSF shows APPC 
> output could be unintentionally retaining APPC junk in their output queue 
> that has no useful function and which would be better to purge in a more 
> timely fashion.
> Joel C Ewing
>
> On 06/17/2016 02:11 PM, Jesse 1 Robinson wrote:
>> In the case of (2), Mark Zelden already explained why most of us have never 
>> seen Ann. His post reminded me of the severe performance problem when 
>> including APPC output. That goes back a long way, and I don't know if it's 
>> still a problem, but I agree with him that most shops have turned off APPC 
>> stuff SDSF either by old practice or by ongoing default in SDSF. 
>>
>> I really wonder if 'O' is ever used. When I submit a job to pull sysmods 
>> from Shopz, I can see in DA up to two additional tasks running at the same 
>> time presumably to handle the USS work. They are never called 'O' or 'U' 
>> anything. And there's 'no displayable data' when they're selected.  
>>
>> .
>> .
>> .
>> J.O.Skip Robinson
>> Southern California Edison Company
>> Electric Dragon Team Paddler
>> SHARE MVS Program Co-Manager
>> 323-715-0595 Mobile
>> 626-302-7535 Office
>> robin...@sce.com
>>
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
>> On Behalf Of Charles Mills
>> Sent: Friday, June 17, 2016 10:59 AM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: (External):Re: Where is format of Job ID documented?
>>
>> Thanks. Dr. Merrill came closest to the answer I was looking for. The real 
>> question behind the question was "if I am processing JOB ID's what should I 
>> expect to see, and if I am presenting them to people who have never heard of 
>> JES, what should they expect to see and what does it mean?"
>>
>> Charles
>>
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
>> On Behalf Of Tony Harminc
>> Sent: Friday, June 17, 2016 10:48 AM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: Where is format of Job ID documented?
>>
>> On 15 June 2016 at 16:38, Charles Mills  wrote:
>>
>>> Yeah, I know, JOBn or Tnnn.
>>>
>>> Is there a formal description somewhere? Where?
>>>
>> It seems to me there are at least two quite different questions here:
>>
>> 1) What is the acceptable syntax for a Job ID?
>>
>> 2) What formats are seen "in the wild", and perhaps
>>
>> 3) What are the circumstances in which each can be generated?
>>
>> I think the answer to (1) is straightforward: The (perhaps obsolescent but 
>> still valid) description of a Job ID as supported by TSO's IKJPARS is "The 
>> jobname can have an optional job identifier. Each job identifier is a 
>> maximum of eight alph

Re: Where is format of Job ID documented?

[Jesse 1 Robinson]

How could I determine if APPC output is clogging my spool? I don't see any at 
the moment.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Joel C. Ewing
Sent: Saturday, June 18, 2016 6:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Where is format of Job ID documented?

We always auto-purged older held output known to be past its usefulness and for 
some categories of output that usefulness was a matter of hours not days. 

My recollection is that after APPC came upon the scene we had to modify the 
held-output purge command sequences or APPC output wasn't touched. 
Makes me wonder if the folks seeing terrible performance when SDSF shows APPC 
output could be unintentionally retaining APPC junk in their output queue that 
has no useful function and which would be better to purge in a more timely 
fashion.
Joel C Ewing

On 06/17/2016 02:11 PM, Jesse 1 Robinson wrote:
> In the case of (2), Mark Zelden already explained why most of us have never 
> seen Ann. His post reminded me of the severe performance problem when 
> including APPC output. That goes back a long way, and I don't know if it's 
> still a problem, but I agree with him that most shops have turned off APPC 
> stuff SDSF either by old practice or by ongoing default in SDSF. 
>
> I really wonder if 'O' is ever used. When I submit a job to pull sysmods from 
> Shopz, I can see in DA up to two additional tasks running at the same time 
> presumably to handle the USS work. They are never called 'O' or 'U' anything. 
> And there's 'no displayable data' when they're selected.  
>
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-302-7535 Office
> robin...@sce.com
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Charles Mills
> Sent: Friday, June 17, 2016 10:59 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: Where is format of Job ID documented?
>
> Thanks. Dr. Merrill came closest to the answer I was looking for. The real 
> question behind the question was "if I am processing JOB ID's what should I 
> expect to see, and if I am presenting them to people who have never heard of 
> JES, what should they expect to see and what does it mean?"
>
> Charles
>
> -Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Tony Harminc
> Sent: Friday, June 17, 2016 10:48 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Where is format of Job ID documented?
>
> On 15 June 2016 at 16:38, Charles Mills  wrote:
>
>> Yeah, I know, JOBn or Tnnn.
>>
>> Is there a formal description somewhere? Where?
>>
> It seems to me there are at least two quite different questions here:
>
> 1) What is the acceptable syntax for a Job ID?
>
> 2) What formats are seen "in the wild", and perhaps
>
> 3) What are the circumstances in which each can be generated?
>
> I think the answer to (1) is straightforward: The (perhaps obsolescent but 
> still valid) description of a Job ID as supported by TSO's IKJPARS is "The 
> jobname can have an optional job identifier. Each job identifier is a maximum 
> of eight alphanumeric characters, the first of which must be an alphabetic 
> character or one of the special characters $, #, @." So the TSO commands 
> CANCEL,STatus, and OUTput  will enforce this, and perhaps others will too. 
> Whether anything in the MVS Subsystem Interface enforces these rules I don't 
> know, but I'd guess it's very unlikely. How it would return an indication of 
> invalidity is one question, aside from the general un-SSIness of checking. So 
> then of course each Job Entry Subsystem can do whatever it likes as fas as 
> checking/enforcing, and those rules will presumably be stricter than the 
> basic syntax.
>
> (2) has been much discussed already. I must say I've never seen an 
> Annn-format Job ID, but surely APPC is more than obsolescent now, and has 
> been for many years. In theory anyone can write a JES, and that JES could 
> have whatever rules it likes, but in practice I don't think anyone is really 
> going to be writing a JESx except perhaps as a learning exercise.
>
> (3) is a matter of anecdotes combined with actual knowledge of the code.
> Job IDs are generated by various 

Re: Where is format of Job ID documented?

[Joel C. Ewing]

We always auto-purged older held output known to be past its usefulness
and for some categories of output that usefulness was a matter of hours
not days. 

My recollection is that after APPC came upon the scene we had to modify
the held-output purge command sequences or APPC output wasn't touched. 
Makes me wonder if the folks seeing terrible performance when SDSF shows
APPC output could be unintentionally retaining APPC junk in their output
queue that has no useful function and which would be better to purge in
a more timely fashion.
Joel C Ewing

On 06/17/2016 02:11 PM, Jesse 1 Robinson wrote:
> In the case of (2), Mark Zelden already explained why most of us have never 
> seen Ann. His post reminded me of the severe performance problem when 
> including APPC output. That goes back a long way, and I don't know if it's 
> still a problem, but I agree with him that most shops have turned off APPC 
> stuff SDSF either by old practice or by ongoing default in SDSF. 
>
> I really wonder if 'O' is ever used. When I submit a job to pull sysmods from 
> Shopz, I can see in DA up to two additional tasks running at the same time 
> presumably to handle the USS work. They are never called 'O' or 'U' anything. 
> And there's 'no displayable data' when they're selected.  
>
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler 
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-302-7535 Office
> robin...@sce.com
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Charles Mills
> Sent: Friday, June 17, 2016 10:59 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: Where is format of Job ID documented?
>
> Thanks. Dr. Merrill came closest to the answer I was looking for. The real 
> question behind the question was "if I am processing JOB ID's what should I 
> expect to see, and if I am presenting them to people who have never heard of 
> JES, what should they expect to see and what does it mean?"
>
> Charles
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Tony Harminc
> Sent: Friday, June 17, 2016 10:48 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Where is format of Job ID documented?
>
> On 15 June 2016 at 16:38, Charles Mills  wrote:
>
>> Yeah, I know, JOBn or Tnnn.
>>
>> Is there a formal description somewhere? Where?
>>
> It seems to me there are at least two quite different questions here:
>
> 1) What is the acceptable syntax for a Job ID?
>
> 2) What formats are seen "in the wild", and perhaps
>
> 3) What are the circumstances in which each can be generated?
>
> I think the answer to (1) is straightforward: The (perhaps obsolescent but 
> still valid) description of a Job ID as supported by TSO's IKJPARS is "The 
> jobname can have an optional job identifier. Each job identifier is a maximum 
> of eight alphanumeric characters, the first of which must be an alphabetic 
> character or one of the special characters $, #, @." So the TSO commands 
> CANCEL,STatus, and OUTput  will enforce this, and perhaps others will too. 
> Whether anything in the MVS Subsystem Interface enforces these rules I don't 
> know, but I'd guess it's very unlikely. How it would return an indication of 
> invalidity is one question, aside from the general un-SSIness of checking. So 
> then of course each Job Entry Subsystem can do whatever it likes as fas as 
> checking/enforcing, and those rules will presumably be stricter than the 
> basic syntax.
>
> (2) has been much discussed already. I must say I've never seen an 
> Annn-format Job ID, but surely APPC is more than obsolescent now, and has 
> been for many years. In theory anyone can write a JES, and that JES could 
> have whatever rules it likes, but in practice I don't think anyone is really 
> going to be writing a JESx except perhaps as a learning exercise.
>
> (3) is a matter of anecdotes combined with actual knowledge of the code.
> Job IDs are generated by various programs, and can also come in off the wire 
> via NJE. Remotes systems such as RSCS don't have the concept of a Job ID, so 
> normally JES2 generatoes a J-type one of its own. If there is an inbound one 
> that doesn't match the rules, then what? I don't know, but it shouldn't be 
> hard to find out. Ah - looking at the NJE headers reminds me that it's a 
> binary (16-bit!) job *number* that comes in, and then JES2 has bit flags to 
> say that it's a batch job or a started task. No TSO... Anyway
>
>


-- 
Joel C. Ewing,Bentonville, AR   jcew...@acm.org 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AW: Re: Where is format of Job ID documented?

[Peter Hunkeler]

>The real question behind the question was "if I am processing JOB ID's what 
>should I expect to see, and if I am presenting them to people who have never 
>heard of JES, what should they expect to see and what does it mean?"




What does it mean to people that have not heard of JES? I guess such people the 
have not much knowledge about z/OS either. In that case, I'd say don't tell 
them anything about the jobid at all. Why? Because it is not telling you much 
anyway.
If I run a shell command from TSO, it will normally be run in my TSO address 
space, tos the jobid associated with this command would be Tnnn. If I run 
the command in batch, it might be running   in the batch job's AS or in a UNIX 
initiator AS (BPXAS), so the jobid would be Jnnn or Snnn, resp.. And if 
the same command is run from an STC, it mit be running in the STC's AS or again 
in a UNIX initiator AS, but the jobid will be Snnn in both cases.


But even standard MVS services might be run as STC or as batch job. Some run 
CICS or IMS as STC, some as batch job. So, CICS/IMS will show up as either 
Snnn or Jnnn.


--
Peter Hunkeler



--
Peter Hunkeler

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Jesse 1 Robinson]

In the case of (2), Mark Zelden already explained why most of us have never 
seen Ann. His post reminded me of the severe performance problem when 
including APPC output. That goes back a long way, and I don't know if it's 
still a problem, but I agree with him that most shops have turned off APPC 
stuff SDSF either by old practice or by ongoing default in SDSF. 

I really wonder if 'O' is ever used. When I submit a job to pull sysmods from 
Shopz, I can see in DA up to two additional tasks running at the same time 
presumably to handle the USS work. They are never called 'O' or 'U' anything. 
And there's 'no displayable data' when they're selected.  

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: Friday, June 17, 2016 10:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Where is format of Job ID documented?

Thanks. Dr. Merrill came closest to the answer I was looking for. The real 
question behind the question was "if I am processing JOB ID's what should I 
expect to see, and if I am presenting them to people who have never heard of 
JES, what should they expect to see and what does it mean?"

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tony Harminc
Sent: Friday, June 17, 2016 10:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

On 15 June 2016 at 16:38, Charles Mills  wrote:

> Yeah, I know, JOBn or Tnnn.
>
> Is there a formal description somewhere? Where?
>

It seems to me there are at least two quite different questions here:

1) What is the acceptable syntax for a Job ID?

2) What formats are seen "in the wild", and perhaps

3) What are the circumstances in which each can be generated?

I think the answer to (1) is straightforward: The (perhaps obsolescent but 
still valid) description of a Job ID as supported by TSO's IKJPARS is "The 
jobname can have an optional job identifier. Each job identifier is a maximum 
of eight alphanumeric characters, the first of which must be an alphabetic 
character or one of the special characters $, #, @." So the TSO commands 
CANCEL,STatus, and OUTput  will enforce this, and perhaps others will too. 
Whether anything in the MVS Subsystem Interface enforces these rules I don't 
know, but I'd guess it's very unlikely. How it would return an indication of 
invalidity is one question, aside from the general un-SSIness of checking. So 
then of course each Job Entry Subsystem can do whatever it likes as fas as 
checking/enforcing, and those rules will presumably be stricter than the basic 
syntax.

(2) has been much discussed already. I must say I've never seen an 
Annn-format Job ID, but surely APPC is more than obsolescent now, and has 
been for many years. In theory anyone can write a JES, and that JES could have 
whatever rules it likes, but in practice I don't think anyone is really going 
to be writing a JESx except perhaps as a learning exercise.

(3) is a matter of anecdotes combined with actual knowledge of the code.
Job IDs are generated by various programs, and can also come in off the wire 
via NJE. Remotes systems such as RSCS don't have the concept of a Job ID, so 
normally JES2 generatoes a J-type one of its own. If there is an inbound one 
that doesn't match the rules, then what? I don't know, but it shouldn't be hard 
to find out. Ah - looking at the NJE headers reminds me that it's a binary 
(16-bit!) job *number* that comes in, and then JES2 has bit flags to say that 
it's a batch job or a started task. No TSO... Anyway


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Charles Mills]

Thanks. Dr. Merrill came closest to the answer I was looking for. The real 
question behind the question was "if I am processing JOB ID's what should I 
expect to see, and if I am presenting them to people who have never heard of 
JES, what should they expect to see and what does it mean?"

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tony Harminc
Sent: Friday, June 17, 2016 10:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

On 15 June 2016 at 16:38, Charles Mills  wrote:

> Yeah, I know, JOBn or Tnnn.
>
> Is there a formal description somewhere? Where?
>

It seems to me there are at least two quite different questions here:

1) What is the acceptable syntax for a Job ID?

2) What formats are seen "in the wild", and perhaps

3) What are the circumstances in which each can be generated?

I think the answer to (1) is straightforward: The (perhaps obsolescent but 
still valid) description of a Job ID as supported by TSO's IKJPARS is "The 
jobname can have an optional job identifier. Each job identifier is a maximum 
of eight alphanumeric characters, the first of which must be an alphabetic 
character or one of the special characters $, #, @." So the TSO commands 
CANCEL,STatus, and OUTput  will enforce this, and perhaps others will too. 
Whether anything in the MVS Subsystem Interface enforces these rules I don't 
know, but I'd guess it's very unlikely. How it would return an indication of 
invalidity is one question, aside from the general un-SSIness of checking. So 
then of course each Job Entry Subsystem can do whatever it likes as fas as 
checking/enforcing, and those rules will presumably be stricter than the basic 
syntax.

(2) has been much discussed already. I must say I've never seen an 
Annn-format Job ID, but surely APPC is more than obsolescent now, and has 
been for many years. In theory anyone can write a JES, and that JES could have 
whatever rules it likes, but in practice I don't think anyone is really going 
to be writing a JESx except perhaps as a learning exercise.

(3) is a matter of anecdotes combined with actual knowledge of the code.
Job IDs are generated by various programs, and can also come in off the wire 
via NJE. Remotes systems such as RSCS don't have the concept of a Job ID, so 
normally JES2 generatoes a J-type one of its own. If there is an inbound one 
that doesn't match the rules, then what? I don't know, but it shouldn't be hard 
to find out. Ah - looking at the NJE headers reminds me that it's a binary 
(16-bit!) job *number* that comes in, and then JES2 has bit flags to say that 
it's a batch job or a started task. No TSO... Anyway

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Tony Harminc]

On 15 June 2016 at 16:38, Charles Mills  wrote:

> Yeah, I know, JOBn or Tnnn.
>
> Is there a formal description somewhere? Where?
>

It seems to me there are at least two quite different questions here:

1) What is the acceptable syntax for a Job ID?

2) What formats are seen "in the wild", and perhaps

3) What are the circumstances in which each can be generated?

I think the answer to (1) is straightforward: The (perhaps obsolescent but
still valid) description of a Job ID as supported by TSO's IKJPARS is "The
jobname can have an optional job identifier. Each job identifier is a
maximum of eight alphanumeric characters, the first of which must be an
alphabetic character or one of the special characters $, #, @." So the TSO
commands CANCEL,STatus, and OUTput  will enforce this, and perhaps others
will too. Whether anything in the MVS Subsystem Interface enforces these
rules I don't know, but I'd guess it's very unlikely. How it would return
an indication of invalidity is one question, aside from the general
un-SSIness of checking. So then of course each Job Entry Subsystem can do
whatever it likes as fas as checking/enforcing, and those rules will
presumably be stricter than the basic syntax.

(2) has been much discussed already. I must say I've never seen an
Annn-format Job ID, but surely APPC is more than obsolescent now, and
has been for many years. In theory anyone can write a JES, and that JES
could have whatever rules it likes, but in practice I don't think anyone is
really going to be writing a JESx except perhaps as a learning exercise.

(3) is a matter of anecdotes combined with actual knowledge of the code.
Job IDs are generated by various programs, and can also come in off the
wire via NJE. Remotes systems such as RSCS don't have the concept of a Job
ID, so normally JES2 generatoes a J-type one of its own. If there is an
inbound one that doesn't match the rules, then what? I don't know, but it
shouldn't be hard to find out. Ah - looking at the NJE headers reminds me
that it's a binary (16-bit!) job *number* that comes in, and then JES2 has
bit flags to say that it's a batch job or a started task. No TSO... Anyway
- Friday speculation. Worth every penny you pay for it...

Tony H.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[John McKown]

On Fri, Jun 17, 2016 at 11:59 AM, saul anthony babonas 
wrote:

> Years ago when my then employer started using the OMVS technology the ESM
> was CA TOP SECRET. Processes failed because the inherited user did not have
> access to the STC "facility". TS allows you to control the ability to
> initiate a started task. Upon some head scratching analysis "holy cow, this
> stuff coming from the dark side uses mini STCS to do their thing."
> So we had to allow any user who did OMVS processes the ability to initiate
> a started task.
> I have long since forgotten which processes (oh, like I ever knew)
> become started tasks. We figured all of them but never tested in order to
> be positive.
> Wish I would have learned better.
>
>
​A UNIX process is usually started via a fork() or spawn() service. The
closest that I can think of is if you use JES2 WLM initiators and do a $SJ​
command to which causes JES2 to start a new WLM initiator and select the
given job. What the fork() does is try to find an "idle" BPXAS "initiator".
If there is one, it tells that to run the UNIX work. If there is not an
idle BPXAS started task, the UNIX kernel will do an internal start of it
and force it to run the new process. When the fork()'d process terminates,
the BPXAS "initiator" will stay around for some period of time waiting for
more work. If it does not get any work, it will "time out" and terminate. I
call it an initiator because it really is running the initiator program -
IEFIIC - but with a special PARM= value.


-- 
"Pessimism is a admirable quality in an engineer. Pessimistic people check
their work three times, because they're sure that something won't be right.
Optimistic people check once, trust in Solis-de to keep the ship safe, then
blow everyone up."
"I think you're mistaking the word optimistic for inept."
"They've got a similar ring to my ear."

>From "Star Nomad" by Lindsay Buroker:

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[saul anthony babonas]

Years ago when my then employer started using the OMVS technology the ESM was 
CA TOP SECRET. Processes failed because the inherited user did not have access 
to the STC "facility". TS allows you to control the ability to initiate a 
started task. Upon some head scratching analysis "holy cow, this stuff coming 
from the dark side uses mini STCS to do their thing."
So we had to allow any user who did OMVS processes the ability to initiate a 
started task.
I have long since forgotten which processes (oh, like I ever knew) become 
started tasks. We figured all of them but never tested in order to be positive.
Wish I would have learned better.



Sent via the Samsung Galaxy Note® 4, an AT&T 4G LTE smartphone


 Original message 
From: Tom Marchant <000a2a8c2020-dmarc-requ...@listserv.ua.edu>
Date: 6/17/2016 6:25 AM (GMT-08:00)
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

On Thu, 16 Jun 2016 22:03:36 -0400, Robert A. Rosenberg wrote:

>At 15:43 -0700 on 06/16/2016, Charles Mills wrote about Re: Where is
>format of Job ID documented?:
>
>>Thanks. Anyone ever see an 'O'? Or a Mount?
>
>I think Mount is a Started Task and thus is S. OTOH: It might run
>under Master Scheduler not JES.

IIRC, there three ways in MVS to create an address space: Start, Logon and 
Mount.

So, is mount a started task? I don't know, but my guess is "no".

Job ID is a JES construct, and I wouldn't expect JES to be involved in Mount.

IIRC, JES3 assigns Job ID differently from JES2.

--
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[John McKown]

On Fri, Jun 17, 2016 at 8:25 AM, Tom Marchant <
000a2a8c2020-dmarc-requ...@listserv.ua.edu> wrote:

> On Thu, 16 Jun 2016 22:03:36 -0400, Robert A. Rosenberg wrote:
>
> >At 15:43 -0700 on 06/16/2016, Charles Mills wrote about Re: Where is
> >format of Job ID documented?:
> >
> >>Thanks. Anyone ever see an 'O'? Or a Mount?
> >
> >I think Mount is a Started Task and thus is S. OTOH: It might run
> >under Master Scheduler not JES.
>
> IIRC, there three ways in MVS to create an address space: Start, Logon and
> Mount.
>
> So, is mount a started task? I don't know, but my guess is "no".
>

​You guessed wrong. It is a started task, transcript below​:

C000 LIH1 16169 08:38:54.09 TSH009H1 0290  M
SYSDA,VOL=(SL,LIHTS1),USE=PRIVATE
 008 LIH1 16169 08:38:54.11  0094  IRR812I PROFILE
IEEVMPCR.* (G) IN THE STARTED CLASS WAS USED 917
 917 0094  TO START
IEEVMPCR WITH JOBNAME IEEVMPCR.
 020 LIH1 16169 08:38:54.15 STC37740 0094  $HASP100 MOUNTON
STCINRDR
 400 LIH1 16169 08:38:54.21 STC37740 0094  $HASP373 MOUNT
 STARTED
 000 LIH1 16169 08:38:54.22 STC37740 0094  IEF403I MOUNT -
STARTED - TIME=08.38.54
 000 LIH1 16169 08:38:54.26 STC37740 0094  IEF404I MOUNT -
ENDED - TIME=08.38.54
 400 LIH1 16169 08:38:54.27 STC37740 0094  $HASP395 MOUNT
 ENDED
 000 LIH1 16169 08:38:55.25  0294  IEA989I SLIP TRAP
ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=00BA.



>
> Job ID is a JES construct, and I wouldn't expect JES to be involved in
> Mount.
>
> IIRC, JES3 assigns Job ID differently from JES2.
>
> --
> Tom Marchant
>
>

-- 
"Pessimism is a admirable quality in an engineer. Pessimistic people check
their work three times, because they're sure that something won't be right.
Optimistic people check once, trust in Solis-de to keep the ship safe, then
blow everyone up."
"I think you're mistaking the word optimistic for inept."
"They've got a similar ring to my ear."

>From "Star Nomad" by Lindsay Buroker:

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Tom Marchant]

On Thu, 16 Jun 2016 22:03:36 -0400, Robert A. Rosenberg wrote:

>At 15:43 -0700 on 06/16/2016, Charles Mills wrote about Re: Where is
>format of Job ID documented?:
>
>>Thanks. Anyone ever see an 'O'? Or a Mount?
>
>I think Mount is a Started Task and thus is S. OTOH: It might run
>under Master Scheduler not JES.

IIRC, there three ways in MVS to create an address space: Start, Logon and 
Mount.

So, is mount a started task? I don't know, but my guess is "no".

Job ID is a JES construct, and I wouldn't expect JES to be involved in Mount.

IIRC, JES3 assigns Job ID differently from JES2.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AW: Re: Where is format of Job ID documented?

[Peter Hunkeler]

>... OTOH: It might run under Master Scheduler not JES.




Makes perfect sense to me. Firstly MOUNT is an MVS command, and secondly, one 
would not be (or have been) able to MOUNT a volume when JESx was down.


--
Peter Hunkeler



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AW: Re: Where is format of Job ID documented?

[Peter Hunkeler]

>Isn't the APPC initiator structure a complete clone of JES2? In other words, 
>it has its own rules and JES2 has no relation whatsoever with APPC jobs or its 
>jobids?




As stated in another post I'm not too familir with APPC, but is there anything 
prohibiting an APPC program from dynamically allocating a SYSOUT file? If not, 
JESx must know about that address space and thus the Annn number would be 
managed by JESx the same way JESx is managing the number for TSU, STC, and 
batch jobs.


--
Peter Hunkeler



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AW: Re: Where is format of Job ID documented?

[Peter Hunkeler]

>>I guess IBM's thinking is that we should just treat it as a magic cookie. It 
>>is guaranteed to be 8 EBCDIC characters that will identify a job or the like. 
>>End of story.
>>
>Used to be 7, IIRC.




Don't you mix that up with TSO Userids which are restricted to 7 charactrers?


--
Peter Hunkeler



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AW: Re: Where is format of Job ID documented?

[Peter Hunkeler]

>
>Hmmm.  If a batch job spawns (not forks) a subprocess with _BPX_SHAREAS=YES
wouldn't that subprocess run under the parent's JobID; no BPXAS, no STC?



Local child processes, started via local spawn(), or attach_exec(), or 
attach_execmvs(), are run in the same address space as the parent process. I.e. 
in the TSO, batch job initiator, APPC initiator or STC address space. (Don't 
know much about APPC programs, but I assume there is nothing prohibiting then 
to use UNIX services.) The same applies to the case when an non-UNIX program is 
being dubbed because it is using A UNIX service now, i.e. when it becomes a 
UNIX process.


Jobname and jobid are address space level attributes, not task or process level.


Non-local child processes, started via fork(), or non-local spawn(), *always* 
run in UNIX initiator address space, aka BPXAS.


BPXAS was introduced with OS/390 V1.3 (I seem to remember). Before that, APPC 
initiators were used to provide a home for non-local child processes.


--
Peter Hunkeler




--
Peter Hunkeler

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Robert A. Rosenberg]

At 15:43 -0700 on 06/16/2016, Charles Mills wrote about Re: Where is 
format of Job ID documented?:



Thanks. Anyone ever see an 'O'? Or a Mount?

Charles


I think Mount is a Started Task and thus is S. OTOH: It might run 
under Master Scheduler not JES.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Mark Zelden]

On Thu, 16 Jun 2016 19:09:44 -0500, Paul Gilmartin  wrote:

>On Thu, 16 Jun 2016 18:58:56 -0500, Mark Zelden wrote:
>
>>From a JOBID standpoint, mount gets and STCid. OMVS processes
>>also get an STCid as does BPXAS. 
>> 
>Hmmm.  If a batch job spawns (not forks) a subprocess with _BPX_SHAREAS=YES
>wouldn't that subprocess run under the parent's JobID; no BPXAS, no STC?
>

Yes, thanks for catching that.  The STCid I'm seeing in my PS command are 
all because the parents are STCs.  If I submitted one of those STCs as
a batch job I would see JOBn.

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Paul Gilmartin]

On Thu, 16 Jun 2016 18:58:56 -0500, Mark Zelden wrote:

>From a JOBID standpoint, mount gets and STCid. OMVS processes
>also get an STCid as does BPXAS. 
> 
Hmmm.  If a batch job spawns (not forks) a subprocess with _BPX_SHAREAS=YES
wouldn't that subprocess run under the parent's JobID; no BPXAS, no STC?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Mark Zelden]

From a JOBID standpoint, mount gets and STCid. OMVS processes
also get an STCid as does BPXAS. If you use the SDSF PS command
you can see the STC number.  So as far as I know there is only 4:

JOBn / Jnnn  
STCn /  Snnn
TSUn / Tnnn
Annn 

I guess the RANGE= parm for JOBDEF in the JES2 manual that was referenced
in another post could / should be updated to include the Annn reference. 

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/





On Thu, 16 Jun 2016 15:43:39 -0700, Charles Mills  wrote:

>Thanks. Anyone ever see an 'O'? Or a Mount?
>
>Charles
>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
>Behalf Of Mark Zelden
>Sent: Thursday, June 16, 2016 3:26 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Where is format of Job ID documented?
>
>>I wrote some code in 1996 for an SMFACTRT exit. Darned if I can 
>>remember where  I got these, but here's what I coded for:
>> 
>>'J' JOB  
>>'S'STC
>>'T'TSU 
>>'A'ASCH/APPC 
>>'O'OMVS/USS 
>> 
>>After all these years, I'm pretty sure I've never seen 'A' or 'O' even 
>>though we run both APPC/ASCH and OMVS/USS. Never saw or coded for Mount.
>
>The default for seeing APPC in SDSF is "APPC OFF" for performance reasons.  
>Performance of some displays can be poor with APPC ON if you use it.   
>
>My client uses ITIM (IBM Tivoli Identity Manager) and there is a RACF agent on 
>z/OS that uses APPC to communicate with a server.  I just issued "APPC ON" in 
>SDSF and did "H ALL" with a prefix of the jobname I knew was out there.  It 
>took a few minutes to get the display back with 32K results, but you can see 
>the Annn JOBIDs in SDSF.
>
>
>SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 136,427 LINE 1-54 (32940)
>COMMAND INPUT ===> sysnameSCROLL ===
>PREFIX=IT*  DEST=(ALL)  OWNER=*  SYSNAME=   
>NP   JOBNAME  JobIDOwnerPrty C ODisp Dest   Max-RC  
> ITIMCMD  A0006429 ITIAGNT   144 Y HOLD  LOCAL  CC  
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Paul Gilmartin]

On 2016-06-16 16:10, Jesse 1 Robinson wrote:
> I wrote some code in 1996 for an SMFACTRT exit. Darned if I can remember 
> where I got these, but here's what I coded for:
> 
> 'J' JOB 
> 'S'STC   
> 'T'TSU
> 'A'ASCH/APPC
> 'O'OMVS/USS
> 
> After all these years, I'm pretty sure I've never seen 'A' or 'O' even though 
> we run both APPC/ASCH and OMVS/USS. Never saw or coded for Mount.
> 
Well, I just ran the EXEC:
/* Rexx */ signal on novalue;  /*
   test
*/
trace R
parse source O.3
say BPXWDYN( 'alloc rtddn(O.1) sysout(R) msg(2)' )
O.2 = USERID()
address MVS 'EXECIO 3 DISKW' O.1 '(finis stem O.'
say O.1

from a ssh session and from a TSO OMVS session with *different*
userIDs.  Both show JobID = STC04488, which happens to appear
in SYSLOG as a recently started BPXAS task.

(Hey!  They fixed something!  I ran my EXEC from a fully qualified
path when its directory was not in my environment PATH.  That used
not to work.)

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Charles Mills]

Thanks. Anyone ever see an 'O'? Or a Mount?

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mark Zelden
Sent: Thursday, June 16, 2016 3:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

>I wrote some code in 1996 for an SMFACTRT exit. Darned if I can 
>remember where  I got these, but here's what I coded for:
> 
>'J' JOB  
>'S'STC
>'T'TSU 
>'A'ASCH/APPC 
>'O'OMVS/USS 
> 
>After all these years, I'm pretty sure I've never seen 'A' or 'O' even 
>though we run both APPC/ASCH and OMVS/USS. Never saw or coded for Mount.

The default for seeing APPC in SDSF is "APPC OFF" for performance reasons.  
Performance of some displays can be poor with APPC ON if you use it.   

My client uses ITIM (IBM Tivoli Identity Manager) and there is a RACF agent on 
z/OS that uses APPC to communicate with a server.  I just issued "APPC ON" in 
SDSF and did "H ALL" with a prefix of the jobname I knew was out there.  It 
took a few minutes to get the display back with 32K results, but you can see 
the Annn JOBIDs in SDSF.


SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 136,427 LINE 1-54 (32940)
COMMAND INPUT ===> sysnameSCROLL ===
PREFIX=IT*  DEST=(ALL)  OWNER=*  SYSNAME=   
NP   JOBNAME  JobIDOwnerPrty C ODisp Dest   Max-RC  
 ITIMCMD  A0006429 ITIAGNT   144 Y HOLD  LOCAL  CC  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Mark Zelden]

>I wrote some code in 1996 for an SMFACTRT exit. Darned if I can remember where
> I got these, but here's what I coded for: 
> 
>'J' JOB  
>'S'STC
>'T'TSU 
>'A'ASCH/APPC 
>'O'OMVS/USS 
> 
>After all these years, I'm pretty sure I've never seen 'A' or 'O' even though 
>we run
>both APPC/ASCH and OMVS/USS. Never saw or coded for Mount. 

The default for seeing APPC in SDSF is "APPC OFF" for performance reasons.  
Performance of some displays can be poor with APPC ON if you use it.   

My client uses ITIM (IBM Tivoli Identity Manager) and there is a RACF agent on 
z/OS that uses APPC to communicate with a server.  I just issued "APPC ON" in
SDSF and did "H ALL" with a prefix of the jobname I knew was out there.  It 
took a few minutes to get the display back with 32K results, but you can
see the Annn JOBIDs in SDSF.


SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 136,427 LINE 1-54 (32940)
COMMAND INPUT ===> sysnameSCROLL ===
PREFIX=IT*  DEST=(ALL)  OWNER=*  SYSNAME=   
NP   JOBNAME  JobIDOwnerPrty C ODisp Dest   Max-RC  
 ITIMCMD  A0006429 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006430 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006431 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006432 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006433 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006434 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006435 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006436 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006440 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006439 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006437 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006438 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006441 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006442 ITIAGNT   144 Y HOLD  LOCAL  CC  
 ITIMCMD  A0006443 ITIAGNT   144 Y HOLD  LOCAL  CC  



Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Jesse 1 Robinson]

I wrote some code in 1996 for an SMFACTRT exit. Darned if I can remember where 
I got these, but here's what I coded for:

'J' JOB 
'S'STC   
'T'TSU
'A'ASCH/APPC
'O'OMVS/USS

After all these years, I'm pretty sure I've never seen 'A' or 'O' even though 
we run both APPC/ASCH and OMVS/USS. Never saw or coded for Mount.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vernooij, CP (ITOPT1) - KLM
Sent: Thursday, June 16, 2016 7:45 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Where is format of Job ID documented?

Out of interest, I did some research.

The $JBIDBLD macro documents:
JOBTYPE=Specifies a label, or a register that contains the address, of the job 
type flag byte (JOB, STC, TSU) used to construct the job ID. The job type flag 
byte must be defined. 
Valid job types, and the bit settings for each are: 
job typeflag bit settingbatch 
jobxx   00
STCxx   01
TSUxx   10

(no more, no less?)

Other doc only speaks of:
JES2 JOBID such as J12345, JOB12345, S12345, STC12345, T12345, TSU12345

Isn't the APPC initiator structure a complete clone of JES2? In other words, it 
has its own rules and JES2 has no relation whatsoever with APPC jobs or its 
jobids?

Kees.


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: 16 June, 2016 15:46
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

Annoying that it is not documented.

I guess IBM's thinking is that we should just treat it as a magic cookie. It is 
guaranteed to be 8 EBCDIC characters that will identify a job or the like. End 
of story.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Robinson, Dave (GE Capital NonGE)
Sent: Thursday, June 16, 2016 1:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Where is format of Job ID documented?

I was once told that there were five. One for APPC as you said, and another for 
MOUNT requests.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: 15 June 2016 22:05
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXT: Re: Where is format of Job ID documented?

I was specifically wondering what could appear in the first position or first 
three positions. Is J(OB), S(TC) and T(SU) the complete set? I thought I seemed 
to remember A-something for APPC transactions? No? Anything else?


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Vernooij, CP (ITOPT1) - KLM]

That is the clue: 
SMF30JNM is described as:
JES job identifier. Jobs scheduled by the APPC/MVS transaction scheduler (ASCH) 
start with an “A” followed by a seven-digit number.

Ann jobs are no JES2 jobs, but ASCH jobs and do not follow JES2 rules, but 
follow APPC rules.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Norbert Friemel
Sent: 16 June, 2016 16:29
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

On Wed, 15 Jun 2016 14:05:09 -0700, Charles Mills wrote:

>I was specifically wondering what could appear in the first position or first 
>three positions. Is J(OB), S(TC) and T(SU) the complete set? I thought I 
>seemed to remember A-something for APPC transactions? No? Anything else?
>
>Charles
>

"A" + seven digits in SMF30JNM? 
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieag200/rec30ids.htm

Norbert Friemel

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Vernooij, CP (ITOPT1) - KLM]

Out of interest, I did some research.

The $JBIDBLD macro documents:
JOBTYPE=Specifies a label, or a register that contains the address, of the job 
type flag byte (JOB, STC, TSU) used to construct the job ID. The job type flag 
byte must be defined. 
Valid job types, and the bit settings for each are: 
job typeflag bit settingbatch 
jobxx   00
STCxx   01
TSUxx   10

(no more, no less?)

Other doc only speaks of:
JES2 JOBID such as J12345, JOB12345, S12345, STC12345, T12345, TSU12345

Isn't the APPC initiator structure a complete clone of JES2? In other words, it 
has its own rules and JES2 has no relation whatsoever with APPC jobs or its 
jobids?

Kees.


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: 16 June, 2016 15:46
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

Annoying that it is not documented.

I guess IBM's thinking is that we should just treat it as a magic cookie. It is 
guaranteed to be 8 EBCDIC characters that will identify a job or the like. End 
of story.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Robinson, Dave (GE Capital NonGE)
Sent: Thursday, June 16, 2016 1:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Where is format of Job ID documented?

I was once told that there were five. One for APPC as you said, and another for 
MOUNT requests.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: 15 June 2016 22:05
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXT: Re: Where is format of Job ID documented?

I was specifically wondering what could appear in the first position or first 
three positions. Is J(OB), S(TC) and T(SU) the complete set? I thought I seemed 
to remember A-something for APPC transactions? No? Anything else?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Greg Shirey]

The JES2 Init & Tuna reference notes this in the description of the RANGE 
initialization statement: 

RANGE=n[,m]|1,
Specifies the range of numbers (1 through 99) which JES2 will assign as 
JOBIDs to jobs which originated on the local node. 
The integer n specifies the lowest number (1 through 99) which will be 
assigned as a JES2 job identifier for jobs originating locally.

The integer m specifies the highest number (n+10 through 99) which will be 
assigned as a JES2 job identifier to jobs originating locally. Note that 
setting the upper limit above 99,999 will cause the JOBID format to change from 
CCCN to C0NN where CCC is either JOB, STC, or TSU, and C is J, S, or T. 
  N or NN is a number.

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa400/has2u600110.htm

Greg Shirey
Ben E. Keith Company 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: Wednesday, June 15, 2016 4:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

Thanks. Supports the idea of only three possible prefixes.

Charles

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Norbert Friemel]

On Wed, 15 Jun 2016 14:05:09 -0700, Charles Mills wrote:

>I was specifically wondering what could appear in the first position or first 
>three positions. Is J(OB), S(TC) and T(SU) the complete set? I thought I 
>seemed to remember A-something for APPC transactions? No? Anything else?
>
>Charles
>

"A" + seven digits in SMF30JNM? 
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieag200/rec30ids.htm

Norbert Friemel

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Paul Gilmartin]

On Thu, 16 Jun 2016 06:45:40 -0700, Charles Mills  wrote:

>Annoying that it is not documented.
>
>I guess IBM's thinking is that we should just treat it as a magic cookie. It 
>is guaranteed to be 8 EBCDIC characters that will identify a job or the like. 
>End of story.
> 
Used to be 7, IIRC.

And our site now uses JOB0.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Charles Mills]

Annoying that it is not documented.

I guess IBM's thinking is that we should just treat it as a magic cookie. It is 
guaranteed to be 8 EBCDIC characters that will identify a job or the like. End 
of story.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Robinson, Dave (GE Capital NonGE)
Sent: Thursday, June 16, 2016 1:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Where is format of Job ID documented?

I was once told that there were five. One for APPC as you said, and another for 
MOUNT requests.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: 15 June 2016 22:05
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXT: Re: Where is format of Job ID documented?

I was specifically wondering what could appear in the first position or first 
three positions. Is J(OB), S(TC) and T(SU) the complete set? I thought I seemed 
to remember A-something for APPC transactions? No? Anything else?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Where is format of Job ID documented?

[Robinson, Dave (GE Capital NonGE)]

I was once told that there were five. One for APPC as you said, and another for 
MOUNT requests.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: 15 June 2016 22:05
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXT: Re: Where is format of Job ID documented?

I was specifically wondering what could appear in the first position or first 
three positions. Is J(OB), S(TC) and T(SU) the complete set? I thought I seemed 
to remember A-something for APPC transactions? No? Anything else?

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John McKown
Sent: Wednesday, June 15, 2016 1:54 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

On Wed, Jun 15, 2016 at 3:38 PM, Charles Mills  wrote:

> Yeah, I know, JOBn or Tnnn.
>
> Is there a formal description somewhere? Where?
>
> Charles
>
> ​I don't know if it is "formal" or not, but here:
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ibm.com_support_knowledgecenter_SSLTBW-5F2.1.0_com.ibm.zos.v2r1.ieaa600_iea3a6-5FObtaining-5Fa-5Fjob-5Fidentifier.htm&d=CwIFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=e3tYBLyxxv2bm6qKB_Bu6i8laFMVOfQGTujvsDqIvKU&m=Ol6AFH9voFSUG-AjIuX1EgHHNZPdVs5gOa92TPdmItA&s=lKgCyJbRe43jKAlLGpqfMXOFIYZHwRkO6go0KlBoq78&e=
 


...

Issue an ENDREQ macro after writing a complete job to the internal reader.
The job identifier is returned in the RPLRBAR field of the request parameter 
list (RPL). See z/OS JES2 Commands 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ibm.com_support_knowledgecenter_en_SSLTBW-5F2.1.0_com.ibm.zos.v2r1.hasa200_toc.htm&d=CwIFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=e3tYBLyxxv2bm6qKB_Bu6i8laFMVOfQGTujvsDqIvKU&m=Ol6AFH9voFSUG-AjIuX1EgHHNZPdVs5gOa92TPdmItA&s=_RVCMwwRSNKW8lYaHd7tj2As5_C_wkiEk3Ac-917Kec&e=
 >  or z/OS JES3 Commands 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ibm.com_support_knowledgecenter_en_SSLTBW-5F2.1.0_com.ibm.zos.v2r1.iatb300_toc.htm&d=CwIFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=e3tYBLyxxv2bm6qKB_Bu6i8laFMVOfQGTujvsDqIvKU&m=Ol6AFH9voFSUG-AjIuX1EgHHNZPdVs5gOa92TPdmItA&s=hdLQu7T3dXmluQgG5NlznwD9fUgUeNmmRVv7ccXppfQ&e=
 > for details about the job identifier.
RPLRBAR is an 8-byte field. The first 3 bytes, xxx, are the characters JOB, TSU 
or STC. The remaining 5 bytes, n, represent the five digits of the job 

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Charles Mills]

Thanks. Supports the idea of only three possible prefixes.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of J R
Sent: Wednesday, June 15, 2016 2:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

$JBIDBLD in KnowledgeCenter. 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Charles Mills]

I was specifically wondering what could appear in the first position or first 
three positions. Is J(OB), S(TC) and T(SU) the complete set? I thought I seemed 
to remember A-something for APPC transactions? No? Anything else?

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John McKown
Sent: Wednesday, June 15, 2016 1:54 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

On Wed, Jun 15, 2016 at 3:38 PM, Charles Mills  wrote:

> Yeah, I know, JOBn or Tnnn.
>
> Is there a formal description somewhere? Where?
>
> Charles
>
> ​I don't know if it is "formal" or not, but here:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaa600/iea3a6_Obtaining_a_job_identifier.htm


...

Issue an ENDREQ macro after writing a complete job to the internal reader.
The job identifier is returned in the RPLRBAR field of the request parameter 
list (RPL). See z/OS JES2 Commands 
<https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa200/toc.htm>
 or z/OS JES3 Commands
<https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.iatb300/toc.htm>
for
details about the job identifier.
RPLRBAR is an 8-byte field. The first 3 bytes, xxx, are the characters JOB, TSU 
or STC. The remaining 5 bytes, n, represent the five digits of the job 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[J R]

$JBIDBLD in KnowledgeCenter. 

Sent from my iPhone

> On Jun 15, 2016, at 16:39, Charles Mills  wrote:
> 
> Yeah, I know, JOBn or Tnnn.
> 
> Is there a formal description somewhere? Where?
> 
> Charles 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Sri h Kolusu]

Charles,


Perhaps this earlier discussion might help? (The postings from Klaus  and 
it also has Barry Merri's routine too)

https://groups.google.com/d/msg/bit.listserv.ibm-main/AC6LGZ2Pc2M/0lx26TmgRboJ


Kolusu

IBM Mainframe Discussion List  wrote on 
06/15/2016 01:38:50 PM:

> From: Charles Mills 
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 06/15/2016 01:39 PM
> Subject: Where is format of Job ID documented?
> Sent by: IBM Mainframe Discussion List 
> 
> Yeah, I know, JOBn or Tnnn.
> 
> Is there a formal description somewhere? Where?
> 
> Charles 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Charles Mills]

Thank you, Doctor.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Barry Merrill
Sent: Wednesday, June 15, 2016 1:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Where is format of Job ID documented?

NO, but MXG has discovered these possibilities:


/* THIS ROUTINE EXPECTS JCTJOBID AND JOB AS 8-BYTE CHARACTERS, */
 /* AND SUBSYS AS A 4-BYTE CHARACTER AS INPUT.  */

 /* JCTJOBID OF ONE LETTER AND 7 DIGITS EXIST, BUT THE MAXIMUM  */
 /* JESNR IS 99 BECAUSE THE 1ST WHEN SEVEN IS ALWAYS ZERO.  */

 /* IT CREATES THE 4-BYTE CHARACTER TYPETASK AND NUMERIC JESNR  */
 /* IT IS %INCLUDE-D AFTER JCTJOBID AND SUBSYS EXIST.   */

 TYPETASK='';
 JESNR=.;
 IF SUBSYS=''  THEN SUBSYS=''; /*EARLY ASIDS,TMNT */
 IF JCTJOBID=JOB OR (JCTJOBID LE ' ' AND SUBSYS='STC')
 OR (JCTJOBID EQ 'MSTR' AND SUBSYS='SMS') THEN DO;
   JESNR=.;
   TYPETASK='STC';
 END;
 ELSE DO;
   IF INPUT(SUBSTR(JCTJOBID,2,7),?? 7.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,2,7),?? 7.);
 TYPETASK=SUBSTR(JCTJOBID,1,1);
   END;
   ELSE IF INPUT(SUBSTR(JCTJOBID,3,6),?? 6.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,3,6),?? 6.);
 TYPETASK=SUBSTR(JCTJOBID,1,2);
   END;
   ELSE IF INPUT(SUBSTR(JCTJOBID,4,5),?? 5.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,4,5),?? 5.);
 TYPETASK=SUBSTR(JCTJOBID,1,3);
   END;
   ELSE IF INPUT(SUBSTR(JCTJOBID,5,4),?? 4.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,5,4),?? 4.);
 TYPETASK=SUBSTR(JCTJOBID,1,4);
   END;
   IF SUBSYS='TCP ' THEN TYPETASK='TCP ';
   ELSE IF SUBSYS='PSF ' THEN TYPETASK='PSF ';
   ELSE IF SUBSYS='VPS ' THEN TYPETASK='VPS ';
   ELSE IF TYPETASK=:'J' THEN DO;
 IF  SUBSYS='TSO ' THEN TYPETASK='TSU ';
 ELSE IF SUBSYS='JES2' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='JES3' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='STC ' THEN TYPETASK='STC ';
 ELSE IF SUBSYS='OMVS' THEN TYPETASK='OMVS';
 ELSE   TYPETASK='JOB ';
   END;
   ELSE IF TYPETASK=:'O' OR SUBSYS='OMVS' THEN TYPETASK='OMVS';
   ELSE IF TYPETASK=:'G' THEN TYPETASK='JOBG';
   ELSE IF TYPETASK=:'S' THEN TYPETASK='STC ';
   ELSE IF TYPETASK=:'A' THEN TYPETASK=SUBSYS;/*ASCH-OR-OMVS:CH16.150*/
   ELSE IF TYPETASK=:'T' THEN TYPETASK='TSU ';
   ELSE IF TYPETASK=:'I' AND SUBSYS='STC' THEN TYPETASK='STC  ';
   ELSE DO;
 IF  SUBSYS='STC ' THEN TYPETASK='STC ';
 ELSE IF SUBSYS='TSO ' THEN TYPETASK='TSU ';
 ELSE IF SUBSYS='JES2' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='JES3' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='STC ' THEN TYPETASK='STC ';
 ELSE IF SUBSYS='OMVS' THEN TYPETASK='OMVS';
 ELSE DO;
   IF PRODUCT='' THEN PRODUCT='';;
   IF SUBTYPE=.  THEN SUBTYPE=.;
   IF PRODUCT='PERFMON ' AND SUBTYPE=3 THEN DO;
 TYPETASK='STC';
 SUBSYS='PERFMON';
       END;
     END;
   END;
   IF TYPETASK=' ' THEN DO;
 BADVJESN+1;
 IF BADVJESN LE 2 THEN
   PUT '*** WARNING - TYPETASK NOT DECODED: ' /  +10
   _N_= SYSTEM= ID= SUBTYPE= JOB=
   JCTJOBID= SUBSYS= TYPETASK= JESNR= ;
   END;
   &MACJESN;
 END;
  /* END OF MEMBER VGETJESN - GET JESNR AND TYPETASK FROM JCTJOBID */

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Charles Mills
Sent: Wednesday, June 15, 2016 3:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Where is format of Job ID documented?

Yeah, I know, JOBn or Tnnn.

Is there a formal description somewhere? Where?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[John McKown]

On Wed, Jun 15, 2016 at 3:38 PM, Charles Mills  wrote:

> Yeah, I know, JOBn or Tnnn.
>
> Is there a formal description somewhere? Where?
>
> Charles
>
> ​I don't know if it is "formal" or not, but here:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaa600/iea3a6_Obtaining_a_job_identifier.htm


...

Issue an ENDREQ macro after writing a complete job to the internal reader.
The job identifier is returned in the RPLRBAR field of the request
parameter list (RPL). See z/OS JES2 Commands

 or z/OS JES3 Commands

for
details about the job identifier.
RPLRBAR is an 8-byte field. The first 3 bytes, xxx, are the characters JOB,
TSU or STC. The remaining 5 bytes, n, represent the five digits of the
job number. See z/OS JES2 Initialization and Tuning Guide

 or z/OS JES3 Initialization and Tuning Guide

 for more information.
...
​
The format of job numbers being displayed as part of command responses or
messages can change depending on whether JES2 is set up to support greater
than 65K jobs. When job numbers are potentially greater than 99,999, the
format for job numbers is as follows: if the maximum allowed job number
(high value of the JOBDEF RANGE= statement) is above 99,999, the job number
format is J0nn. This format is used unless the job number range is
decreased below 100,000. Similarly, STCn becomes S0nn and TSUn
becomes T0nn.

​...​

​​


-- 
"Pessimism is a admirable quality in an engineer. Pessimistic people check
their work three times, because they're sure that something won't be right.
Optimistic people check once, trust in Solis-de to keep the ship safe, then
blow everyone up."
"I think you're mistaking the word optimistic for inept."
"They've got a similar ring to my ear."

>From "Star Nomad" by Lindsay Buroker:

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Barry Merrill]

NO, but MXG has discovered these possibilities:


/* THIS ROUTINE EXPECTS JCTJOBID AND JOB AS 8-BYTE CHARACTERS, */
 /* AND SUBSYS AS A 4-BYTE CHARACTER AS INPUT.  */

 /* JCTJOBID OF ONE LETTER AND 7 DIGITS EXIST, BUT THE MAXIMUM  */
 /* JESNR IS 99 BECAUSE THE 1ST WHEN SEVEN IS ALWAYS ZERO.  */

 /* IT CREATES THE 4-BYTE CHARACTER TYPETASK AND NUMERIC JESNR  */
 /* IT IS %INCLUDE-D AFTER JCTJOBID AND SUBSYS EXIST.   */

 TYPETASK='';
 JESNR=.;
 IF SUBSYS=''  THEN SUBSYS=''; /*EARLY ASIDS,TMNT */
 IF JCTJOBID=JOB OR (JCTJOBID LE ' ' AND SUBSYS='STC')
 OR (JCTJOBID EQ 'MSTR' AND SUBSYS='SMS') THEN DO;
   JESNR=.;
   TYPETASK='STC';
 END;
 ELSE DO;
   IF INPUT(SUBSTR(JCTJOBID,2,7),?? 7.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,2,7),?? 7.);
 TYPETASK=SUBSTR(JCTJOBID,1,1);
   END;
   ELSE IF INPUT(SUBSTR(JCTJOBID,3,6),?? 6.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,3,6),?? 6.);
 TYPETASK=SUBSTR(JCTJOBID,1,2);
   END;
   ELSE IF INPUT(SUBSTR(JCTJOBID,4,5),?? 5.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,4,5),?? 5.);
 TYPETASK=SUBSTR(JCTJOBID,1,3);
   END;
   ELSE IF INPUT(SUBSTR(JCTJOBID,5,4),?? 4.) GT . THEN DO;
 JESNR=INPUT(SUBSTR(JCTJOBID,5,4),?? 4.);
 TYPETASK=SUBSTR(JCTJOBID,1,4);
   END;
   IF SUBSYS='TCP ' THEN TYPETASK='TCP ';
   ELSE IF SUBSYS='PSF ' THEN TYPETASK='PSF ';
   ELSE IF SUBSYS='VPS ' THEN TYPETASK='VPS ';
   ELSE IF TYPETASK=:'J' THEN DO;
 IF  SUBSYS='TSO ' THEN TYPETASK='TSU ';
 ELSE IF SUBSYS='JES2' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='JES3' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='STC ' THEN TYPETASK='STC ';
 ELSE IF SUBSYS='OMVS' THEN TYPETASK='OMVS';
 ELSE   TYPETASK='JOB ';
   END;
   ELSE IF TYPETASK=:'O' OR SUBSYS='OMVS' THEN TYPETASK='OMVS';
   ELSE IF TYPETASK=:'G' THEN TYPETASK='JOBG';
   ELSE IF TYPETASK=:'S' THEN TYPETASK='STC ';
   ELSE IF TYPETASK=:'A' THEN TYPETASK=SUBSYS;/*ASCH-OR-OMVS:CH16.150*/
   ELSE IF TYPETASK=:'T' THEN TYPETASK='TSU ';
   ELSE IF TYPETASK=:'I' AND SUBSYS='STC' THEN TYPETASK='STC  ';
   ELSE DO;
 IF  SUBSYS='STC ' THEN TYPETASK='STC ';
 ELSE IF SUBSYS='TSO ' THEN TYPETASK='TSU ';
 ELSE IF SUBSYS='JES2' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='JES3' THEN TYPETASK='JOB ';
 ELSE IF SUBSYS='STC ' THEN TYPETASK='STC ';
 ELSE IF SUBSYS='OMVS' THEN TYPETASK='OMVS';
 ELSE DO;
   IF PRODUCT='' THEN PRODUCT='';;
   IF SUBTYPE=.  THEN SUBTYPE=.;
   IF PRODUCT='PERFMON ' AND SUBTYPE=3 THEN DO;
 TYPETASK='STC';
 SUBSYS='PERFMON';
       END;
     END;
   END;
   IF TYPETASK=' ' THEN DO;
 BADVJESN+1;
 IF BADVJESN LE 2 THEN
   PUT '*** WARNING - TYPETASK NOT DECODED: ' /  +10
   _N_= SYSTEM= ID= SUBTYPE= JOB=
   JCTJOBID= SUBSYS= TYPETASK= JESNR= ;
   END;
   &MACJESN;
 END;
  /* END OF MEMBER VGETJESN - GET JESNR AND TYPETASK FROM JCTJOBID */

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Charles Mills
Sent: Wednesday, June 15, 2016 3:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Where is format of Job ID documented?

Yeah, I know, JOBn or Tnnn.

Is there a formal description somewhere? Where?

Charles 

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Where is format of Job ID documented?

[Charles Mills]

Yeah, I know, JOBn or Tnnn.

Is there a formal description somewhere? Where?

Charles 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN