× 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.


  1.  Home
  2. MIDRANGE-L
  3. October 2017

Re: Passing a packed field into a command string

On 10/10/2017 12:11 PM, Peter Dow wrote:
The thing to remember is that when you call a program from the command
line, or in a SBMJOB command, numeric parameters are passed as packed
decimal 15.5.

Yes! They are parameters from the caller to the SBMJOB, and they are
literals from the SBMJOB command line to D1C716.

In your situation, program D1C716 could define the numeric *ENTRY
parameters as packed decimal 15.5, then eval/z-add those to mhseq,
wManifest2 and wManifest3.

The time tested alternative is to create a very simple *CMD, and set the
command processing program to be D1C716. Invoking the program from the
command line would be dead simple, the job log would have sane looking
entries, and programs that already call D1C716 with packed(7: 2)
variables would continue to work as-is.
--buck


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.