I am not sure how your EXEC worked, so I went to the manuals for information on
EVENTLOG:
Programs can use Spool Data Set Browse (SDSB) to allocate SPOOL data sets. The
data set being requested is specified by passing the JES data set name along
with a SPOOL browse token to MVS™ dynamic allocation. When the data set is
allocated, the data set can be read using one of two methods:
Using the compatibility interface (DCB, GET).
Using the ACB/RPL interface.
You use the compatibility interface when synchronous sequential access is
required. You use the ACB/RPL interface when random access to the spool file is
required, or when asynchronous processing is required.
The EVENTLOG data set is allocated automatically for every batch job, started
task, and TSO user. It contains machine readable records and is intended to be
processed by applications. The data set is not considered to be SYSOUT so it
cannot be accessed by SAPI/PSO/FSS. It is non-printable and non-spinnable.
EVENTLOG is processed using the Spool Data Set Browse interface.
As mentioned earlier in this section, the Spool Data Set Browse (SDSB)
interface can be used to access the EVENTLOG data set. The data set name
supplied to SDSB can be used to control which records in the EVENTLOG data set
are returned to the application on a GET request. For example, if the
application wants to retrieve all records in the EVENTLOG data set it can use
the fully qualified data set name:
userid.jobname.jobID.D008.EVENTLOG
Additionally, the application can use the following logical data set name to
retrieve all EVENTLOG records:
userid.jobname.jobID.EVENTLOG
Additionally, the application can use the following logical data set name to
retrieve all EVENTLOG records:
userid.jobname.jobID.EVENTLOG
For more information on specifying a data set name to the SDSB interface, see
Specifying the Data Set Name (DALDSNAM).
So it looks like there is a jes2 spool dataset name you should be able to
access, but not with IEBGENER. Something called the Spool Data Set Browse
Lizette
> -Original Message-
> From: Lizette Koehler [mailto:stars...@mindspring.com]
> Sent: Tuesday, November 03, 2015 6:50 PM
> To: 'IBM Mainframe Discussion List'
> Subject: RE: s013-68 on JES2 EVENTLOG?
>
> So not to answer your question,
> But I use John McKown's JES2DISK Rexx that uses ISFEXEC and writes to Unix or
> PS
> datasets.
> https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997
>
>
> Maybe that would work for you.
>
> Lizette
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Paul Gilmartin
> > Sent: Tuesday, November 03, 2015 3:25 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: s013-68 on JES2 EVENTLOG?
> >
> > We just got our z/OS 2.2 system up. So I regression tested an EXEC
> > that unloads the spool files of a job to UNIX files.
> >
> > It uses IEBGENER to copy each DDNAME allocated by SDSF to a UNIX file.
> > It specifies no DCB attributes on SYSUT2, leaving it to IEBGENER to
> > copy to SYSUT2 those supplied by SDSF.
> >
> > I see a spool file I've never seen before: stepname JES2, ddname
> > EVENTLOG, which fails with:
> >
> >7 8 EVENTLOG: RECFM=U LRECL=32760 CHARS=,,,
> > IEC141I 013-68,IFG0196L,user,$STCTSO1,SYS00196
> > IEA995I SYMPTOM DUMP OUTPUT
> > SYSTEM COMPLETION CODE=013 REASON CODE=0068
> > TIME=14.50.12 SEQ=00083 CPU= ASID=0063
> > PSW AT TIME OF ERROR 075C1000 80A26336 ILC 2 INTC 0D
> > NO ACTIVE MODULE FOUND
> > NAME=UNKNOWN
> > DATA AT PSW 00A26330 - 4100302C 0A0D010D A7E5014B
> >
> > SDSF "SE" opens it OK with profile:
> > =PROF> ISFEDIT (VARIABLE - 32760)RECOVERY ONNUMBER
> > OFF
> >
> > Why is this breaking IEBGENER? (I don't know how to extract BLKSIZE
> > from SDSF.)
> >
> > Might it be because IEBGENER might be DCBE-ignorant?
> >
> > -- gil
> >
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
