|
Lots of issues using call in batch. Instead of using call, have you tried a custom command for this program? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Dan Rasch <drasch@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 02/19/2003 08:49 AM Please respond to Midrange Systems Technical Discussion To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc: Fax to: Subject: 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. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.