I handle SBMJOB in these cases by placing quotes around all strings at their full declared length. Here is a snipet of my typical SBMJOB command string creation. I then use QCMDEXC to execute it. RQSDTA(''CALL PRPPRC PARM(+ ''''' *CAT &UNAME *CAT ''''' + ''''' *CAT &UWSID *CAT ''''' + ''''' *CAT &GROUP *CAT ''''' + -----Original Message----- From: Brendan Bispham [mailto:firstname.lastname@example.org] Sent: Friday, March 08, 2002 9:47 AM To: email@example.com Subject: Re: [C400-L] CMD parms On Friday 08 March 2002 13:08, Ulrich, Kent wrote: > String argements coming in from a command or a CL program will have a > length equal to the declared length in the command or CL program with no > null terminator. ie, in my case they're all 9999 However I have debugged the CL and found that's the cause... Although I always thought if the PARM length = the DCL length then you dont get this problem. Looking at the archives it seems you definitly dont get it with SBMJOB, but I'll have to look into this furhter... Thanks, _______________________________________________ This is the C programming iSeries / AS400 (C400-L) mailing list To post a message email: C400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/c400-l or email: C400-Lfirstname.lastname@example.org Before posting, please take a moment to review the archives at http://archive.midrange.com/c400-l.