SBMJOB inserting nulls

A fellow developer submitted this question to IBM and was told 
they know of a problem.  Anyone else experience this:

While testing V5R2, I discovered when a parm 34 characters
long is used in the SBMJOB command and the last characters
blank (Hex value '40'), the submitted program receives the 
last character corrupted with a hex value of '00'.
 
If an 80 character parm containing an 'X' in positions 1-3
is submitted, all characters after position 33 will have a
hex value of '00' when received.

I verified the parms in both programs are the same length and 
type.

If the same program is called instead of submitted the parm 
is passed correctly.

Parm in the SBMJOB command:
         Value in Hexadecimal                              
         * . . . + . . . . 1 . . . . + . . . . 2 . . . . + 
'XXX  '  E7E7E740404040404040404040404040404040404040404040
    +26  404040404040404040

Parm as received by the submitted program:
         Value in Hexadecimal                              
         * . . . + . . . . 1 . . . . + . . . . 2 . . . . + 
'XXX  '  E7E7E740404040404040404040404040404040404040404040
    +26  404040404040404000

Has anyone else had this problem?  Is there a PTF to fix 
this?



Dan Rasch - because if the human species concentrated on the really 
important things in life, there would be a shortage of fishing poles!
IBM Certified twice....... but still a couple PTFs away from Nirvana.