Re: 3000-char CL parm padded with hex zeros -- MIDRANGE-L

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

Subject: Re: 3000-char CL parm padded with hex zeros
From: Dan <dan27649@xxxxxxxxx>
Date: Tue, 26 Apr 2016 10:37:09 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

In this case, the %trim(C3000) would be concatenated in the middle of
another string used in PGMB.

- Dan

On Tue, Apr 26, 2016 at 10:32 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

Another thing to consider is this,
if you %trim(my3000char)
you are still going to end up with x'00' for the trimmed off characters
unless you store it into a variable length character field.
What hexadecimal value do you expect to see in those trimmed off
characters?

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.