I do it the old fashioned way: 1. Create GDGs 2. Issue a ' Don:
I do it the old fashioned way: 1. Create GDGs 2. Issue a 'WRITELOG' and then a proc like this //HPYCPY PROC //IEFPROC EXEC PGM=IASXWR00,PARM='PL',REGION=200K //* //* WTR TO SCOOP UP SYSLOGS //* //IEFRDER DD SPACE=(CYL,(10,10),RLSE),UNIT=SYSDA, // DSN=ADCD.RACF.HARDCOPY(+1), // DISP=(NEW,CATLG), // DCB=(BLKSIZE=13030,LRECL=137,BUFL=13030,BUFNO=2,RECFM=VBM), // VOL=SER=WRK001 Scott J Ford ________________________________ From: Donald Likens <[email protected]> To: [email protected] Sent: Wed, June 8, 2011 9:47:38 AM Subject: SYSLOG saving In my previous shop we used a product called $AVRS to retain SYSLOG for an extended period of time. I assume other shops do the same. I need it in a readable format with as much information as possible. If you save SYSLOG at your shop, how do you do it? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
