I suppose strongly a classic error when SBMJOBing a call. When command processor inspect the sbmjob command, it reformat each parameter in as many segments of 32 chars as necessary. If one parameter value length is too short, parameter is truncated abnormaly. detection : add a ending mark to your parameters (IE any not blank character at the end) correction :make your params one char long more than usage request, load each end char with a "*" for example, remove it in the called cl. ========================================================= There are two correct ways to handle this. First, the CMD() parameter is the wrong one to use if the command will be CALL. The parameters to CALL are not typed, so the command prompter/analyzer cannot handle their values as needed. Don't use CMD() -- the correct parameter to use is RQSDTA(). In fact, what the CMD() parameter actually does is to cause the command prompter/analyzer to process the CMD() value to generate a string that gets used as the RQSDTA(). You can see a small bit of evidence of that by looking at the RQSDTA() default value and reading the <help> for it. Second, if you really insist on using CMD(), then define a command to put into the parameter. A command definition will provide the parameter attributes that are missing when you choose to leave them out by using CALL. Tom

I suppose strongly a classic error when SBMJOBing a call. When command processor inspect the sbmjob command, it reformat each parameter in as many segments of 32 chars as necessary. If one parameter value length is too short, parameter is truncated abnormaly. detection : add a ending mark to your parameters (IE any not blank character at the end) correction :make your params one char long more than usage request, load each end char with a "*" for example, remove it in the called cl. ========================================================= There are two correct ways to handle this. First, the CMD() parameter is the wrong one to use if the command will be CALL. The parameters to CALL are not typed, so the command prompter/analyzer cannot handle their values as needed. Don't use CMD() -- the correct parameter to use is RQSDTA(). In fact, what the CMD() parameter actually does is to cause the command prompter/analyzer to process the CMD() value to generate a string that gets used as the RQSDTA(). You can see a small bit of evidence of that by looking at the RQSDTA() default value and reading the <help> for it. Second, if you really insist on using CMD(), then define a command to put into the parameter. A command definition will provide the parameter attributes that are missing when you choose to leave them out by using CALL. Tom