|
midrange.com
Jim,
Like you I'm at a loss as to why/how the file was changed to CCSID 500.
But if on V4R5 it was created with CRTPF NACMNOC RCDLEN(1655) then it would
have been created with CCSID 65535 and a default CCSID of whatever your
default job CCSID was at the time. Have you tried CHGPF NACMNOC
CCSID(65535)? I'm not sure that this will fix your situation but should
get you back closer to the environment you were on with V4R5.
I'm hesitant to suggest using CCSID(37) as your current experience with
CCSID(500) and the resultant mapping ftp is using suggests that ftp really
thinks you're getting a vertical line (ASCII x'7C') from the other system.
Can you by chance confirm what value is being used on the other system?
Bruce Vining
"Jim Franz"
<franz400@xxxxxxx
r.com> To
Sent by: "Midrange Systems Technical
midrange-l-bounce Discussion"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
03/11/2005 08:52 Subject
AM Re: v5r3 ftp and cpyfrmimpf and
ccsid
Please respond to
Midrange Systems
Technical
Discussion
Bruce - (see question below)
from DSPPFM of NACMNOC
E]MAITLAND
CBDCCEDCDC
5B41933154
from DSPFFD
Record Format Information
Record format . . . . . . . . . . . . . . . : NACMNOC
Number of fields . . . . . . . . . . . . . : 1
Field Level Information
Data Field Buffer Buffer Field
Field Type Length Length Position Usage
NACMNOC CHAR 1655 1655 1 Both
Coded Character Set Identifier . . . . . : 500
If I change (rebuild) NACMNOC to ccsid 37, when ftp gets file
from unix system with (replace - will that create any problem or set
ccsid back to 500? (I'm in a fog when it comes to understanding what
happens during ftp in this area). I have no idea how file ever set to 500.
It was originally a CRTPF with record length 1655 and the default ccsid
(which i think is 37). This maybe happened on restore from v4r5 to v5r3
system?
When we converted we did not recognize problem - their is special logic for
data between these separators.
jim
----- Original Message -----
From: "Bruce Vining" <bvining@xxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, March 11, 2005 9:10 AM
Subject: Re: v5r3 ftp and cpyfrmimpf and ccsid
>
>
>
>
> Jim,
>
> I don't know how you are looking at NACMNOC, but x'BB' in CCSID 500 is
the
> vertical line ( | ) and x'5A' the right square bracket. As CCSID 37 has
> the vertical line defined as x'4F' CPYFRMIMPF is doing the correct CCSID
> conversion.
>
> Is it possible that NACMNOC should be tagged as a different CCSID?
>
> Bruce Vining
>
>
>
>
> "Jim Franz"
> <franz400@xxxxxxx
> r.com>
To
> Sent by: <MIDRANGE-L@xxxxxxxxxxxx>
> midrange-l-bounce
cc
> s@xxxxxxxxxxxx
>
Subject
> v5r3 ftp and cpyfrmimpf and ccsid
> 03/10/2005 10:09
> PM
>
>
> Please respond to
> Midrange Systems
> Technical
> Discussion
>
>
>
>
>
>
> Problem since moving to V5R3
> I have a flat file that is received each week via ftp with a get xxx
> (replace
> from a unix server. The file NACMNOC on the i5 has a single field, ccsid
=
> 500.
> CPYFRMIMPF FROMFILE(NACMNOC) TOFILE(NACM400) +
> MBROPT(*REPLACE) RCDDLM(*ALL) +
> DTAFMT(*DLM) STRDLM('"') FLDDLM(',') +
> RPLNULLVAL(*FLDDFT)
> File NACM400 fields are all ccsid = 37
> Everything is converting fine except 1 character.
> The from file has a a hex BB (looks like a right bracket).
> After cpyfrmimpf that character becomes a hex 4F (|).
> My pgm looks for the hex BB to separate parts of the data.
> Worked fine on prev system at V4R5.
> Anything I can do besides recode the rpg?
> jim franz
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-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.
