What version of MPE are you running and are you current on patches?

I was able to locate SR 4701282384 which describes this problem and says it was
fixed back in the 5.0 era.

When callci is used from a batch job such as Apache, CI I/O redirection is done
into a temporary file to capture command output.  This temporary filename is
derived from the POSIX getpid() function, which in turn is derived from the MPE
PID of the current process.

An MPE PID uniquely identifies a process throughout the life of a system.  The
high-order portion of the PID is set to zero at boot time, then gets
incremented at each process creation.  What appears to be happening here is
that your system has created enough processes since boot time such that the PID
can no longer be squeezed into the 7 hex digits used for the callci temporary
filename.

I suspect you will have to reboot your machine to clear this problem.

If you are on MPE 5.5 or greater and are current on patches, then hmmmmm, maybe
this didn't really get fixed or regressed somehow.

- Mark B.

"YU,YONG-NING (HP-PaloAlto,ex1)" wrote:
>
> Hello There,
>
> We had a cgi script (in which use /bin/callci) used for product download but
> was suddenly broken. We could not figure it out what caused the problem. The
> script used to be work fine and still works if I move it to another hp3000
> server which have same Apache web server.
>
> A test script is as below:
> -------------------------------------
> #!/bin/sh
>
> echo "Content-type: text/html"
> echo
> echo
>
> echo "<TITLE> Download Script </TITLE>"
> echo "<H1> Download Script </H1>"
>
> /bin/callci "SHOWTIME"
>
> ------------------------------------------
>
> Sometime I got what I expected as:
>
> Download Script
> WED, SEP 20, 2000, 6:31 PM
>
> but sometime I got :
>
> Download Script
> SHOWTIME >U1095006F.PUB.APACHE ^Too many parameters were given for this
> command. (CIERR 10002)
>
> The Uxxxxxxxx would be changed with different call. The script would be also
> fine if I run it directly in posix shell.
>
> Any comments?
>
> Thanks,
> Yongning Yu