|
I'm doing a cpytoimpf file with rmvblank(*trailing|*both) and it's not
removing blanks. PTF thing maybe? I'm on V5R4. Using this command:
CPYTOIMPF FROMFILE(WCSRTL/VLDIMAGES)
TOSTMF('/tmp/vldimages.csv')
MBROPT(*REPLACE)
STMFCODPAG(*PCASCII)
RCDDLM(*CRLF)
RMVBLANK(*TRAILING)
gives me this file:
200031716 ,"BERN ","389-042
","BERN-389-042.JPG
","MAIN"
400013986 ,"HAM ","T00275-00
","HAM-T00275-00_DTL_1.JPG
","SUPP"
200031717 ,"BERN ","389-333
","BERN-389-333.JPG
","MAIN"
200031717 ,"BERN ","389-333
","BERN-389-333_OPEN.JPG
","SUPP"
800007892 ,"BERN ","COLL-BELMONT
","BERN-COLL-BELMONT.JPG
","MAIN"
200035111 ,"LEA
","SET-SO-203-33-SLEIGH","LEA-SET-SO-203-33-SLEIGH.JPG
","MAIN"
250026804 ,"SSC ","BO500CA-CAMEL
","SSC-BO500CA-CAMEL.JPG
","MAIN"
250026804 ,"SSC ","BO500CA-CAMEL
","SSC-BO500CA-CAMEL_DTL.JPG
","SUPP"
250026805 ,"SSC ","BO500CH-CHOCOLATE
","SSC-BO500CH-CHOCOLATE.JPG
","MAIN"
250026805 ,"SSC ","BO500CH-CHOCOLATE
","SSC-BO500CH-CHOCOLATE_DTL1.JPG
","SUPP"
800008143 ,"SSC ","COLL-MONTIBELLO-DR
","SSC-COLL-MONTIBELLO-DR.JPG
with the fourth field being very long, and all character fields 'untrimmed'.
On Thu, Sep 10, 2009 at 10:30 AM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:
That wouldn't make sense... if you are exporting from a varying,--
there's no blanks to trim.
Perhaps you are thinking of the same parm on the CPYFRMIMPF? There,
trimming trailing blanks makes no sense unless you are importing into
a varying field.
Charles
On Thu, Sep 10, 2009 at 10:23 AM, Michael Ryan <michaelrtr@xxxxxxxxx>
wrote:
I thought that only worked when the character fields are VARYING.list
On Thu, Sep 10, 2009 at 10:14 AM, <darren@xxxxxxxxx> wrote:
Very true, especially if using CPYTOIMPF. Otherwise your fixed lengthfields
can take up a lot of unused space.
FYI, CPYTOIMPF has a 'TRIM' function, if you don't have the benefit of
variable length database fields. Its called RMVBLANK.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
listTo post a message email: RPG400-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
To post a message email: RPG400-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
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.