Transforms are just 1 line DS BASIC logic that can be used inside your job in a derivation or constraint expression. When pre-compiling, the Transform name is expanded to the full logic expression stored. This means that if you change the logic in a Transform, all jobs using it must be recompiled. A...
It's a bad idea to use an after-job routine to run another job. You have limited error checking or recover abilities. You're probably attempting to build a "chain" of jobs, where A runs B, which runs C, which runs D. This is exactly why you should build a Batch job and use your job control logic the...
Craig, you should have kept quiet. I was quite impressed with your ability to transmit thought to the poster and also have the right solution, as odd as the solution is.
Probably not, as the export requires exclusive access to an object when it is being accessed. There is a chance both processes will collide on the same object.
I have LOTS of these. In fact, one per job. Don't worry about these. You have a status, config, log, bp, bp.o, and temp file for every job. Leave them alone. Any time you import a job, these are wiped out and created fresh under a new job number. Anytime you compile a job, some of these are automat...
Triton46 wrote:Is there a list anywhere on the board of files/directories to be routinely cleaned up?
In your uvconfig file there is a temp directory configuration. There's also the "&PH&" directory in every project. During an operational downtime, maybe once a week, clear these directories.
Of all of the bad things that can happen, running a project out of disk space IS THE WORST POSSIBLE THING . Jobs executing can corrupt their logs, configuration, and status files because of insufficient disk space. If ONE SINGLE DEVELOPER has a job open for design and is saving the job, it can corru...