RE: [EXT] Re: Need to replace hex zeroes in a CL variable

Booth,

Winner, Winner Chicken Dinner the next time you come to Jacksonville, Florida.

That worked.

Thanks Very Much,
Danny

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Booth Martin
Sent: Tuesday, November 26, 2019 4:04 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXT] Re: Need to replace hex zeroes in a CL variable

External Email: This is an EXTERNAL email do not click links or open attachments unless you know the content is safe. Please use caution with Urgent Requests.


Would it work to define a workfield, and then move the &FILELABEL into the new field and use the new field?

Another thought is to define a field with value 'X"00"' and the use the
%trim() command with the 2nd parm as the field name?


On 11/26/2019 2:30 PM, Danny Hayes wrote:

First,



V7 R3 -



I have a CL program that is calling another program to get a file name. The field is 256 characters long.

It has the value for the file name and then the rest is populated with hex zeroes.

The file name is then to be used in the CPYTOIMPF command, and it chokes if there are Nulls in the file name.



I tried %TRIM with no second parm, but that only works for blanks.

I tried %Trim using the second parm, but not sure I specified it right:

VALUE(%TRIM(&FILELABEL 'X"00"')) I tried multiple times and this is the only way I got it to compile.



I initialized the fields to blanks, but when they come back to me the file name has those x'00'.



TIA,

Danny





"This email and any attachments, contain Genuine Parts Company confidential information that is proprietary, privileged, and protected by applicable laws. If you have received this message in error and are not the intended recipient, you should not retain, distribute, disclose or use any of this information and you should destroy this email, any attachments or copies therein forthwith. Please notify the sender immediately by email if you have received this email in error."

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&amp;data=02%7C01%7Cdanny_hayes%40genpt.com%7Cb6b2e9d133d34d76411808d772b421af%7Cb439d764f2cb43eaac052e373c83043e%7C0%7C0%7C637103990301330603&amp;sdata=6Ld%2FNmeGezKrOxe4sy4x44TAbx8lzp6a1dt5Tz1dtiQ%3D&amp;reserved=0
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchive.midrange.com%2Fmidrange-l&amp;data=02%7C01%7Cdanny_hayes%40genpt.com%7Cb6b2e9d133d34d76411808d772b421af%7Cb439d764f2cb43eaac052e373c83043e%7C0%7C0%7C637103990301330603&amp;sdata=Kri4aEoxAbBQ3p9n5vbz9sL9UkqHmPnpHvDKpK29uwE%3D&amp;reserved=0.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Famazon.midrange.com&amp;data=02%7C01%7Cdanny_hayes%40genpt.com%7Cb6b2e9d133d34d76411808d772b421af%7Cb439d764f2cb43eaac052e373c83043e%7C0%7C0%7C637103990301330603&amp;sdata=SMvHdS14d83vOXIrxENuL734BctrOeiZJciMWdKQHVo%3D&amp;reserved=0