inconsistent output from dsjob command

[ray.wurlod]

That's just how it works. There is only one log table for the job, whether it is multi-instance or not. It is up to you to filter them once you've obtained them. Director includes appropriate filtering, but dsjob does not. Submit an enhancement request if you think it's a useful feature.

[kcbland]

In the loop that pulls back the log messages, you'll want to put a conditional in there to only use the log message if the jobname.instance is found in the text string. The DS BASIC job control APIs for scanning job logs are not instance-aware, even if using the jobname.instance.

Your change should be fairly simple, if it's a ksh you're only looking at counting the occurences of the jobname in the log line and if greater than 0 then the message pertains so keep it.