I've had something happen twice that is odd.  In a stream job, a CHGROUP
command produces an error saying that it is not programmatically executable.
Here's a shot of the error.

 :   cd cati
 CHGROUP cati
 Command not programmatically executable. (CIERR 12)
 Abort program - Error# 12



 Program terminated in an error state. (CIERR 976)
 REMAINDER OF JOB FLUSHED.
 CPU sec. = 82.  elapsed min. = 3.  SAT, DEC  1, 2001,  2:03 AM.


We actually use a small script called CD which does the chgroup command then
sets a variable.  This command worked fine just a few lines before this.
Has anyone seen this?  What could cause chgroup to fail?  FYI I've never
seen the cd script have a problem and the group we were changing too always
exists.


Thanks!

Allen Porter
Maritz Research, St. Louis
ISO 9001 Registered
      Visit our web site @ <http://www.maritz>research.com




<font size="1">Confidentiality Warning:  This e-mail contains information intended only for the use of the individual or entity named above.  If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, any dissemination, publication or copying of this e-mail is strictly prohibited. The sender does not accept any responsibility for any loss, disruption or damage to your data or computer system that may occur while using data contained in, or transmitted with, this e-mail.   If you have received this e-mail in error, please immediately notify us by return e-mail.  Thank you.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *