|
I handled an interesting support call last night. The failing job had an error because the target of a CPYF CRTFILE(*YES) already existed, the job was trying to create a 'history' file with a filename derived from job date/time. The CPYF failed because the previous run of the job, 24 hours earlier had created the same file that this instance was trying to create. The job is submitted by the built-in job scheduler; and scheduled for submission at midnight. I was surprised (shocked, actually) to see that the job had an 'Entered system time' and 'Start time' of 00:00:01 on August 15, but that the 'Job date' was August 14. Anyone have any explanation for this weirdness, for lack of a better term? Thanks, Joe Joe Henderson The Sharper Image, San Francisco (415) 445-6124 ***************************** NOTICE: All e-mail sent to or from this e-mail address will be received or otherwise recorded by The Sharper Image corporate e-mail system and is subject to archival, monitoring, and review by and/or disclosure to Sharper Image security and other management. This message is intended only for the use of the addressee and may contain information that is privileged and confidential. The contents of this message may contain personal views which are not the views of The Sharper Image. If you are not the intended recipient, dissemination of this communication is prohibited. *****************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.