<SNIP> Hi Wayne, Instead of "ISFEXEC ST", I would've used "ISFEXEC DA OJOB" or ISFEXEC "DA OSTC" (depending upon whether CICS is a Job or Started Task). The reason is that ST shows running Jobs/STCs and already ended Job/STCs (that haven't been Purged).
Regards, David </SNIP> I want all jobs, running or not. This particular example was to obtain any abend information from CEEMSG from any CICS job on the queue. We maintain abend stats in a DB2 table. If we've already captured it, it just gives a -803. Wayne On Mon, Feb 4, 2019 at 11:46 AM David Spiegel <[email protected]> wrote: > Hi Wayne, > Instead of "ISFEXEC ST", I would've used "ISFEXEC DA OJOB" or ISFEXEC > "DA OSTC" (depending upon whether CICS is a Job or Started Task). > The reason is that ST shows running Jobs/STCs and already ended Job/STCs > (that haven't been Purged). > > Regards, > David > > On 2019-02-03 19:20, Wayne Bickerdike wrote: > > Here's how I've pulled the CEEMSG dataset and parsed it for abends. > Adjust > > SYSOUT names to suit. > > > > ARG IPARM > > > > rc=isfcalls('ON') > > > > CICS_REGION = STRIP(IPARM) > > > > /* SET UP JOB CARD AND JCL FOR REMOTE SPUFI EXECUTION */ > > > > CALL JOBSET > > > > /* Access the ST display */ > > > > isfprefix = IPARM > > > > Address SDSF "ISFEXEC ST" > > > > /* Loop for all running CICS jobs */ > > > > Do ix=1 to JNAME.0 > > > > /* if JNAME.ix = IPARM & QUEUE.ix = "EXECUTION" & ACTSYS.ix <> "", */ > > > > if JNAME.ix = IPARM , > > > > then Do > > > > /* Issue the ? (JDS) action against the */ > > > > /* row to list the data sets in the job. */ > > > > Address SDSF "ISFACT ST TOKEN('"TOKEN.ix"') PARM(NP ?)" , > > > > "( prefix jds_" > > > > /* Find the SYSOUT data set and allocate it */ > > > > /* using the SA action character */ > > > > Do jx=1 to jds_DDNAME.0 > > > > if jds_DDNAME.jx = "CEEMSG" then Do > > > > Address SDSF "ISFACT ST TOKEN('"jds_TOKEN.jx"')" , > > > > "PARM(NP SA)" > > > > /* Read the records from the data set and list them. */ > > > > /* The ddname for each allocated data set will be in */ > > > > /* the isfddname stem. Since the SA action was done */ > > > > /* from JDS, only one data set will be allocated. */ > > > > Do kx=1 to isfddname.0 > > > > Say "Now reading" isfdsname.kx > > > > "EXECIO * DISKR" isfddname.kx "(STEM line. FINIS" > > > > Say " Lines read:" line.0 > > > > /* IF NOT, ADD CMD ENV */ > > > > Do lx = 1 to line.0 > > > > /* Say " line."lx "is:" line.lx */ > > > > Call Selrecs > > > > end > > > > end > > > > end > > > > end > > > > end > > > > end > > > > rc=isfcalls('OFF') > > > > EXIT > > > > On Mon, Feb 4, 2019 at 11:16 AM Wayne Bickerdike <[email protected]> > wrote: > > > >> RGEN has plenty of examples. From SDSF command line, RGEN X and roll > your > >> own. > >> > >> > >> > >> On Mon, Feb 4, 2019 at 10:03 AM Paul Gilmartin < > >> [email protected]> wrote: > >> > >>> On Sun, 3 Feb 2019 20:21:23 +0000, Seymour J Metz wrote: > >>> > >>>> Well, there's always XDC, but the basic answer is that it depends on > how > >>> the output datasets were defined. > >>> I've had success using the Rexx interface to SDSF, which allocates a > >>> generated DDNAME > >>> to the SYSOUT. I can use alternate DD list to override IEBGENER's > SYSUT1 > >>> with that name. > >>> IEBGENER copies DCB attributes from (overridden) SYSUT1 to SYSUT2. > >>> > >>> The spool files remain, undisturbed, in the output queue. > >>> > >>>> ________________________________________ > >>>> From: McCabe, Ron > >>>> Sent: Friday, February 1, 2019 2:07 AM > >>>> > >>>> How can I get reports that are in the Output Queue in SDSF to be > >>> re-printed...basically I want them to be processed again. > >>> > >>> -- gil > >>> > >>> ---------------------------------------------------------------------- > >>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>> send email to [email protected] with the message: INFO IBM-MAIN > >>> > >> > >> -- > >> Wayne V. Bickerdike > >> > >> > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
