None of these should need JCL specification to read an existing dataset. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Sri h Kolusu > Sent: Tuesday, January 16, 2018 8:36 AM > To: [email protected] > Subject: Re: DFSORT for HTTP logs - RECFM and BLKSiZE? > > Tim, > > You follow the same rules for JCL. Something like this > > //SORTIN DD PATH='your http log file', > // RECFM=??,LRECL=290,BLKSIZE=?????, > // FILEDATA=TEXT,PATHOPTS=ORDONLY > > > Thanks, > Kolusu > DFSORT Development > IBM Corporation > > > > From: Tim Hare <[email protected]> > To: [email protected] > Date: 01/16/2018 09:25 AM > Subject: DFSORT for HTTP logs - RECFM and BLKSiZE? > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > I want to do some simple reporting on my HTTP logs (httpd-log.MMMddYYYY). > I'm coding PARSE= to get the information I want, and I think I understand that > part, but when I run my job SORT complains about RECFM, LRECL, or BLKSIZE. > Viewing the logs, it looks like the record length is 290 (that's what ISPF > view > tells me) but where do I determine RECFM and BLKSIZE? How do I code the > JCL for these beside the PATH= and PATHOPTS= values? > > ---------------------------------------------------------------------- > 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
