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



Bob,
I'm using Advanced Business Link's HSM tool.  I need to load the data into a DS 
and move the DS to the program's output parameter.  So the move to some sort of 
stand-alone field is required.  
Bill
----- Original Message ----- 
From: Bob Cozzi 
To: 'RPG programming on the AS400 / iSeries' 
Sent: Sunday, February 16, 2003 12:40 PM
Subject: RE: Extname problem


Don't know why, but to solve the problem, how about doing this:

Dslfl01A1       e ds                  extname(slfl01a)               
Dslfl01A2       e DS                  extname(slfl01a)  PREFIX(SAV_)

Bob Cozzi 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Bill
Sent: Sunday, February 16, 2003 11:14 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Extname problem


Any ideas on this?

Here's what I have:
---
Fslll01A   if   e           k disk  

Dslfl01A1       e ds                  extname(slfl01a)               
Dslfl01A2         S                   like(slfl01a1)   

after a chain:
move      SLFL01A1       SLFL01A2
---

In slfl01a1 I get the contents of the file.
In slfl01a2 I get garbage in all of the numeric fields that exist in the
file.

If I add a prefix to the file or the EDS it gets worse.  
I've also tried inz; inz(*extfmt) and using a pf as the extname ref;
changing the field to a: subfield & a DS.


What am I doing wrong?

Thanks!
Bill 

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