Re: Service program procedure passing parameters to an external progr am

> All of the necessary variables, including initial values for
> message file and action code are defined within the
> CreateMessage procedure.  For some reason, the
> message id and program name are blank when the
> external CLLE program is executed, but the message file
> and action code have the initial values specified in the definition
> specifications.

I know you said that all the variables are defined in CreateMessage, but is
it possible that they are really defined in some other procedure (or the
mainline) and not passed in via the parameter list?  Where I'm heading is
that if the filled in variables are in another procedure but not passed into
CreateMessage, the variables in CreateMessage will not be populated (because
they're local.)

Another thing to check is that ALL parameters match size and type EVERYWHERE
in the program.  The point being that if there's storage being inadvertently
wiped out, a parameter mismatch could do it.  Along the same lines, see if
you have any OPTIONS(*VARSIZE) parameters but are clearing/MOVEing data into
it.  *VARSIZE variables always need to be dealt with only with the actual
length of the variable provided.

If none of this is any help, I guess it's time to post the CreateMessage
procedure and the parameter list/DCL section of the CL program.
  --buck