Re: (External):Re: Logrec and EREP
Example JCL for the TRENDS situation used to keep a history. This shop elected
not to use GDGs. The EREP9000 contains two control statements but I don't
think they've been touched in over 15 years (they are listed after the JCL)
//*==*
//* 4. MAKE A BACKUP COPY OF THE HISTORY FILE*
//*==*
//COPYHIST EXEC PGM=IEBGENER
//SYSINDD DUMMY
//SYSPRINT DD DUMMY,DCB=BLKSIZE=121 * DUMMY PRINT - DONT NEED
//SYSUT1 DD DSN=SYSTEMS.EREP.PROD.HIST, * MAKING A COPY OF
//DISP=OLD * HISTORY FILE
//SYSUT2 DD DSN=SYSTEMS.EREP.PROD.HISTBKUP, * TO BACKUP FILE
//DISP=OLD *
//*==*
//* 5. CAPTURE LATEST 30 DAY'S HISTORY *
//*==*
//HISTORY EXEC PGM=IFCEREP1,
//REGION=2048K,
// COND=(0,LT,COPYHIST),* DONT RUN IF COPY FAILED
// PARM=('TRENDS',* RUNNING 30 DAY SELECTION
// 'HIST=Y',* FROM HISTORY INPUT
// 'ACC=Y', * ACCUM IN ACCDEV
// 'TABSIZE=768K', * LARGE TABLE
// 'ZERO=N')* DON'T CLEAR LOGREC
//ACCDEV DD DSN=SYSTEMS.EREP.PROD.HIST, * OUTPUT HISTORY FILE
//DISP=OLD *
//ACCINDD DSN=SYSTEMS.EREP.PROD.HISTBKUP, * IS COMBINED FROM
//DISP=OLD * PREVIOUS ONE PLUS
// DD DSN=SYSTEMS.EREP.PROD.DAY,* THE DATA FROM
//DISP=OLD * TODAYS RUN
//DIRECTWK DD UNIT=SYSDA,SPACE=(CYL,(10,5))
//EREPPT DD DUMMY,* DUMMY OUTPUT
//DCB=BLKSIZE=133 * SINCE USING TRENDS AS
//* * RUNNING COPY PROGRAM
//TOURIST DD SYSOUT=*
//SERLOG DD DUMMY
//SYSINDD DSN=DOT2.JOBS.DATA(EREP9000),DISP=SHR
SYSIN statements
*- LIMIT STATEMENTS TO CONTROL OUTPUT ---*
LIMIT 3880,OVRN=1000
*- THIS IMPLIES ALL I/O ADDRESSES ARE UNIQUE *
SYSIMG BASESN=ALL
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: (External):Re: Logrec and EREP
There have been times when I preferred to send raw unformatted LOGREC data if only to create a smaller attachment. But I've never found any way to select a from-to range of raw data, so I end up running EREP just to make use of selection criteria. We all send 'raw' SVC dumps, right? No one would format a dump in order to ship it. As others have said, the ISV request is puzzling and at best poorly worded. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lucas Rosalen Sent: Monday, October 19, 2015 11:43 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Logrec and EREP Maybe they just want a different LOGREC report? You can the description and instructions for each one in these manuals here: http://m.ibm.com/http/www-03.ibm.com/systems/z/os/zos/library/bkserv/v2r1pdf/#IFC (for zOS 2.1) ​Regards, --- *Lucas Rosalen* Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com <lrosa...@br.ibm.com>* LinkedIn: http://br.linkedin.com/in/lrosalen Phone: +48 792 809 198 2015-10-20 1:49 GMT+02:00 Shmuel Metz (Seymour J.) < shmuel+ibm-m...@patriot.net>: > In > <capikfhe902jtfvyv-exettxgvaao1sy2zewnk40l6h8agrq...@mail.gmail.com>, > on 10/19/2015 >at 05:02 PM, Peter <dbajava...@gmail.com> said: > > >I am trying to Understand the Difference between a Logrec Report and > >a EREP report. > > EREP is a program that reports the contents of LOGREC. > > >This question came to my mind when I was working with one of ISV > >vendor. Initially we gave EREP report but later on he wanted to have > >a Logrec Report. > > Ask the ISV for a better educated technician. > > >Could someone please shed light on the above. > > My guess is that you gave him a report on hardware records and he > wanted a report on software records, or he wants the raw records. -- > Shmuel (Seymour J.) Metz, SysProg and JOAT > ISO position; see <http://patriot.net/~shmuel/resume/brief.html> -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
