This is a set of fixes and enhancements to the KMS-FUSION CCL. I have sent them to Jim Downward, and they appear here with his blessing. He is supposed to be working on an entirely new release of CCL, which will fit in with M4.0 (whenever it comes out). That one will undoubtedly be better with 4.0 than this one, but this one works better with 3.2 than his old one. Also in this UIC is a seperate "HEY" task. I find that HEY is so useful, that I want to do it even while CCL is busy, so I yanked it out and made it stand-alone. Ray Van Tassle Motorola 1301 E. Algonquin Rd. Room 4135 Schaumburg, Ill. (312)-576-6017 CCL is great !!!!!!!!! However, it had some bugs and some awkward things in it's operation. I have spent quite some time of fixing it up, as follows: Fixed up some bugs (there are some error messages that go out LUN 5, which is difficult since there is a UNITS=2 in the TKB file). 1. I made it privileged (but it sets itself non-priv), so that it links to the EXEC. it can now use $GTTSK for "HEY" and "-taskname", so you can just say "HEY TKB" 2. Added some validity checks for the ?.CCL file, so that it will catch you if you mess it up (which is very easy for a non-experienced CCL user to do in making his own USERCCL.CCL). Also allowed for null lines comment lines, so that you can read a ?.CCL file without going blind. 3. If it has no command line, it will prompt for one. If it does have to prompt for one, it will also print out each command line before spawning it to MCR. Sometimes this is about the only way to see how to set up your CCL control line, to make it come out right. In essence, for debugging a new CCL command, you type "RUN ...CA." and enter your command to the CCL prompt. 4. The last line of a CCL command does not wait, it passes the OCB (if any) and MCR prompt status (bit T3.MCR) to the spwaned task. This lets CCL get out of the way as quickly as it can, especially when you do a COPY or DEL, etc, which will take a long time, and you can start up another CCL thing (many of our infrequently used programs are run by CCL). This removes the need for the %$ parameter (although it is still in). For those times when you want CCL to stay active for all the programs (for example if you specifically want CCL to tell you about the exit-status) you merely make the last command a null line (which did not used to be legitimate). 5. CCL now prints out a message if a tasks exit status is not SUCCESS, and will quit (with a message), unless it is only WARNING.