Jon, I (and I assure you, a lot of people in IBM) understand the need for this. However, the issue is that, there is no "definitive" value of "current date." Instead of it being a case of "you might burn yourself, so you can't do it." I see it as a case of being able to get it "almost right" which, as Roger Miller puts it so well, is just another way of saying "wrong" Wayne Driscoll Product Developer JME Software LLC NOTE: All opinions are strictly my own.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jon Brock Sent: Thursday, May 17, 2007 1:25 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Date & Time in JCL <deadhorsebeat> . . . and none of those choices are really good, at least for a non-sysprog. I know the reasoning behind not having it as a batch JCL, but it seems a case of "you might burn yourself, so you can't do it." There's a reason it comes up frequently; many people would find it useful. </deadhorsebeat> Jon <snip> Comes up repeatedly. First choice is Scheduling PKG, second choice is ISPF SKELs, more choices include Rexx, CLIST, HLASM to generate JCL and sub to internal reader. </snip> ---------------------------------------------------------------------- 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
