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 Annnnnnn jobid I see in SDSF is displayed as the "TPJOBID" in the
output.
MZELDEN 00000210 $DOS(30087),OUTGRP=ITIMCMD.1.1,LONG
STC30087 00000211 $HASP686 OUTPUT(ASCHINT) 154
154 00000211 $HASP686 OUTPUT(ASCHINT)
OUTGRP=ITIMCMD.1.1,BURST=NO,FCB=****,
154 00000211 $HASP686 FLASH=****,FORMS=STD,HOLD=(NONE),
154 00000211 $HASP686
OFFS=(),OUTDISP=HOLD,PRIORITY=144,
154 00000211 $HASP686 PRMODE=LINE,QUEUE=Y,RECORDS=(6 OF
6),
154 00000211 $HASP686 ROUTECDE=LOCAL,SECLABEL=,
154 00000211 $HASP686 TPJOBID=A0004237,TPJOBN=ITIMCMD,
154 00000211 $HASP686
TSOAVAIL=YES,UCS=****,USERID=ITIAGNT,
154 00000211 $HASP686 WRITER=,REBUILD=NO,
154 00000211 $HASP686 CRTIME=(2016.170,07:04:21)
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:[email protected]
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 <[email protected]> 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:[email protected]] On
>Behalf Of Mark Zelden
>Sent: Sunday, June 19, 2016 1:47 PM
>To: [email protected]
>Subject: Re: Where is format of Job ID documented?
>
>On Sat, 18 Jun 2016 21:00:38 +0000, Jesse 1 Robinson <[email protected]>
>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 Annnnnnn Issue "O" and sort on
>JOBID and look for Annnnnnn
>
>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:[email protected] 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
>[email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
