While it appears that everyone answered your question regarding JES autocommands. I'll tell you that we do use CRON here on the mainrame, but ONLY for what I consider UNIX "busy work". Mostly to run the IBM provides skulker shell script to cleanup garbage in various directories to keep them from filling up. For example /tmp.
00 0 1 * * mv /var/spool/cron/skulker.log /var/spool/cron/skulker.log.old 01 0 * * * /shared/etc/filetouch 10 0 * * * /usr/sbin/skulker -R -l /var/spool/cron/skulker.log /tmp/ 3 I first run a script that just goes out and touches files that need to stay, but don’t get their date/time stamps updated by life of IPL tasks. #!/bin/sh # filetouch # resets last access date/time on in process files in /tmp so that # skulker does not delete them for inactivity. touch -c /tmp/dpi_socket touch -c /tmp/omproute.stderr touch -c /tmp/omproute.stdout touch -c /tmp/pagent.pid touch -c /tmp/pagent.log touch -c /tmp/pagent.log1 touch -c /tmp/pagent.log2 touch -c /tmp/sshd.stderr touch -c /tmp/unix.str then I run skulker against /tmp to delete anything older than 3 days old. We have additional directories I need to set this up for, just haven’t gotten around to it yet. My big thing is that I don’t want CRON to get used as an alternative to the Enterprise Scheduler (in our case TWS), so its limited to this type of house keeping work to begin with. _________________________________________________________________ Dave Jousma Mainframe Engineering, Assistant Vice President [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Sean Gleann Sent: Tuesday, November 6, 2018 3:49 AM To: [email protected] Subject: Anyone using cron? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Hello all I have a need to run a couple of batch jobstreams at the same time every day. The streams are fully developed and they run happily at the required time(s), under control of a couple of JES 'TA' automatic commands: £ T A0001,I=86400,T=00.05,'£VS,''S JOB,N=DLYWORK1''' £ T A0002,I=86400,T=00.10,'£VS,''S JOB,N=DLYWORK2''' ('JOB' is an IEBGENER that copies files to the internal reader) The trouble with that solution is that TA commands are obeyed both at the prescribed times AND at IPL (or JES start?) time. Given that I'm currently working on commissioning a new production system, IPLs are still fairly frequent, and so the timed jobstreams keep resulting in 'unexpected' results. There isn't any cash in the kitty for something like OPC (now Tivoli?) or CA-7, and I've been unable to track down any 'freeware' batch job scheduler (though I'd be happy to be shown the error of my ways on that), so I decided to try using cron instead. Is anybody using cron in this way? Is there anything I should beware of? Sean . ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
