Posted by Bob A on June 04, 2010 at 10:13:58:
compiled an MTB program using a command file.
specified:
SOURCE RDCE.IBS
OBJECT RDCE
LIST B
*
I did this because I added some text to the source, and wanted to make the resulting object have a date after the change date of the source
I checked the original object (106) using FILENT, and it had a "load" size of 48,250
didn't change the source, and checked this with a file comparator
the compile using the command file (107) gave a different "load" size... additionally, the process failed the first time I ran it.
so... I manually recompiled it, which is how I always compile. to get another object (108), and got:
106: 48,250
107: 49,178
108: 48,250
I have yet to get the test files together to verify that 108 works, just as 106 did, but I still have to ask:
why should it make any difference how I compile an object?
what happens when I use a command file to do multiple compiles at once?
why do I get different results?
the only thing I know about the failing object is that it looks like COMMON got stepped on, because the program that died (which was RUN (2 steps later, in fact)) couldn't find a printer name in COMMON. The recompiled program (107) was supposed to put a printer name in COMMON, which would be picked up later. This worked fine in version 106.
I must confess I'm grasping at straws here, since I'm very shaky on interprogram communication using COMMON, but the only thing I can point to is the difference in "load" sizes, leading me to believe that might have something to do with the problem.
BTW... we're running COMET 2008 build 391
Thanx!
Bob "A"
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.