× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Good point - I was thiniking of the SBMJOB scenario - still, write a simple command - it takes care of everything.

Vern

On 10/30/2013 3:18 PM, CRPence wrote:
On 10/30/13 10:38 AM, Charles Wilt wrote:
The system has no way of knowing how big the parm is defined in the
CL. That's the job of the *CMD object.

But default, character parms are passed as char(32) unless the value
has more than 32 characters; in which case the parm is passed at it's
actual size.

However, trailing blanks are trimmed.

If you wanted to pass 'HI' as a char(1024), you'd need to pass: HI
followed by 1022 blanks followed by some non-blank character, for a
total of 1025 characters. The trailing non-blank character will never
be seen by your program.

Alternatively, the the "best" solution in IMHO is to define a *CMD
front end to your program.

A command-line invocation, from the Command-Entry panel [having
pressed the F11="Display full" for the expanded-view, thus allowing
~1300 characters], simply requires the full 1024-bytes of data delimited
by the apostrophe as string-delimiter. There is no need to pass an
extra non-blank character in that case. However when a *CHAR _variable_
has been passed as an element of the PARM in the CALL statement [not
allowed in the *EXEC command-line environment], having been passed
through an additional iteration of the command interpreter, the extra
non-blank character would be required; e.g. for a request such as:
SBMJOB CMD(CALL PGM(pgmname) PARM(&C1024))



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.